How to handle releases #1
Locked
moonmeister
started this conversation in
RFC
Replies: 2 comments 1 reply
-
|
Look into : https://github.com/fastify/releasify |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Even more promising: https://github.com/changesets/action |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This has been implemented. renovate PRs will need changesets added manually for now. Maybe this can be automated in the future. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This may be one of the harder things we need to solve. We can't open this up too broadly for stability and security purposes. But we also want to allow as many people as possible to quickly fix and publish packages.
Automation will be key. This allows there to be clear record of what code got published to NPM from what commit. If this can be accomplished through a pull request system this would allow anyone, even without publish permissions, to prepare a release, and anyone with merge rights could create it.
I'll be playing around with this idea and flushing it out. Please make suggestions, input welcome.
Beta Was this translation helpful? Give feedback.
All reactions