-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add canary release workflow 🐥 #1178
Conversation
|
Tip Once this PR is ready to go, add the This saves us a lot of money by not running the tests before we need them. |
🐥 |
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.
nice work!
currently this adds all releases to git, its possible this may change changesets/action#141 (which would be great) |
What are you changing?
Adds a canary release option to PRs.
Why?
So we can test packages in external consumer codebases (@guardian/transparency-consent do this a lot, so it's needed for #1128).
How does it work?
It is based heavily on similar workflows in guardian/commercial#797 and guardian/consent-management-platform#849 (but with some slight differences):
🐥 Canaries
label to a PR will trigger the release of canary versions of all packages with waiting changesets1Demo
You can see it running on this PR from #1178 (comment) onwards.
Footnotes
This is maybe not expected, but also it's not obvious how you'd get round this. How do you know which package with unreleased changes the user wants to test? It feels like overkill but I think it kind of makes sense. ↩