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
Fix experimental releases for pnpm #9015
Conversation
|
let args = ["--access public", `--tag ${tag}`]; | ||
if (tag === "experimental") { | ||
args.push(`--no-git-checks`); | ||
} else { | ||
args.push("--publish-branch release-next"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By default, pnpm
will only publish from main
. Turn off this check when publishing an experimental from release-experimental-*
and change the allowed publish branch to release-next
for normal releases.
// Sync up the pnpm-lock.yaml file with the new experimental version | ||
if (syncLockFile) { | ||
console.log(chalk.green(" Syncing pnpm lockfile...")); | ||
execSync("pnpm install --no-frozen-lockfile"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to do this with the version bump otherwise the CI run will fail on pnpm install --frozen-lockfile
No description provided.