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

fix publish for stable branch #1724

Merged
merged 1 commit into from
Dec 13, 2023
Merged

fix publish for stable branch #1724

merged 1 commit into from
Dec 13, 2023

Conversation

mansona
Copy link
Member

@mansona mansona commented Dec 13, 2023

we needed to update relase-plan to add an option --publish-branch because by default pnpm only allows you to run pnpm publish on main or master. We are running it on stable and it was hanging in CI because it was prompting to know if you wanted to continue.

This PR prevents that from happening again 👍

@@ -49,7 +49,7 @@ jobs:
registry-url: 'https://registry.npmjs.org'

- name: npm publish
run: pnpm release-plan publish
run: pnpm release-plan publish --publish-branch=stable
Copy link
Collaborator

Choose a reason for hiding this comment

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

don' we want --publish-branch=stable|main, since we merge stable into main frequently?

Copy link
Member Author

Choose a reason for hiding this comment

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

once we sync this it won't be a problem any more. For example #1721 didn't even try to update the yaml branches

also it's better to be explicit with this.

and also we didn't test if that syntax works (if the pnpm docs says it does that's fine but I'm extra cautious around releasing things). We know what this PR has does work because I've done it manually twice.

So in summary, no i don't think we should change this 😂

Copy link
Collaborator

Choose a reason for hiding this comment

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

ah ok, I see what you mean

Legit

@NullVoxPopuli NullVoxPopuli merged commit fd7859c into stable Dec 13, 2023
201 checks passed
@NullVoxPopuli NullVoxPopuli deleted the update-release-plan branch December 13, 2023 19:59
@github-actions github-actions bot mentioned this pull request Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants