Auto publishing and move default branch to latest
#20
Conversation
Activate auto publish Update Build and Publish.yml
|
@Supereg - I had already started the effort around this ( 3.6.x ), then saw that you had published 3.7.0 already. So the GitHub changes are a bit messed up. The beta publishing is active, and production will be after merging |
|
Publish notes are here https://github.com/homebridge/documentation/blob/latest/Repositories.md#supporting-packages Thought about making my simple publishing a shared asset, and will tackle that at some point in the future. |
|
NPM Release published - https://www.npmjs.com/package/bonjour-hap?activeTab=versions Humm, my script does not include a |
Makes it inconsistent with all of our other repos. I think there is no one relying on it currently, but could you fix it for the future to add v prefixes again? |
Simple automated publishing for projects
Automatically publishes beta releases, when a change is pushed to a beta branch
For a latest/production release, workflow must be manually kicked off / started from
Actions --> Build and Publish. ( This is by design to prevent accidental production releases.)Latest release includes a github release
Release Workflow ( Beta --> Production )
1 - Determine what the target version will be for the final release and update the package.json version number ( ie
0.5.6)2 - Create a new branch including the target release version ie
beta-0.5.63 - Commit the updated package.json to the new beta branch. This will trigger a npm release with the beta tag, and npm version set to
0.5.6-beta.0.4 - As updates are made to the beta branch, npm beta releases will be created.
5 - Once the release is complete, and ready for latest/production release, create a pull request to merge the changes into the
latestbranch.6 - After reviews are complete, merge the pull request
7 - For the latest/production release, the workflow must be manually kicked off / started from Actions --> Build and Publish
8 - Delete beta branch