Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publish flow fixes #28050

Merged
merged 4 commits into from Aug 13, 2021
Merged

publish flow fixes #28050

merged 4 commits into from Aug 13, 2021

Conversation

padmaia
Copy link
Member

@padmaia padmaia commented Aug 13, 2021

Tested theses changes end to end in my fork (published under my personal scope with some irrelevant jobs skipped to speed up iteration)

Screen Shot 2021-08-12 at 6 58 37 PM

@ijjk ijjk added the created-by: Next.js team PRs by the Next.js team label Aug 13, 2021
@@ -15,7 +15,7 @@ fi
if [[ $(git describe --exact-match 2> /dev/null || :) =~ -canary ]];
then
echo "Publishing canary"
yarn run lerna publish from-git --npm-tag canary --yes
yarn run lerna publish from-git --npm-tag canary --no-git-reset --yes
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--no-git-reset makes lerna okay with git update-index --skip-worktree. It seems like we would be interested in the feature proposed in this issue.

@padmaia padmaia merged commit 367117e into vercel:canary Aug 13, 2021
@@ -15,7 +15,7 @@ const cwd = process.cwd()

// Copy binaries to package folders, update version, and publish
let nativePackagesDir = path.join(cwd, 'packages/next/build/swc/npm')
let platforms = await (await readdir(nativePackagesDir)).filter(
let platforms = await readdir(nativePackagesDir).filter(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this await readdir still needs to be wrapped

@padmaia padmaia deleted the fix-npm-access branch September 15, 2021 17:06
@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
created-by: Next.js team PRs by the Next.js team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants