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.

Sign up for GitHub

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

Jump to bottom

Auto publishing and move default branch to latest #20

Merged
merged 2 commits into from Mar 26, 2024
Merged

Auto publishing and move default branch to latest #20

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4f454e
Activate auto publish
NorthernMan54 Mar 26, 2024
8531f2a
Merge branch 'latest' into beta-3.7.1
NorthernMan54 Mar 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 11 additions & 7 deletions .github/workflows/Build and Publish.yml
View file
Open in desktop
Expand Up @@ -3,16 +3,20 @@ name: "Build and Publish"
# Simple automated publishing for projects

# Automatically publishes beta releases, when a change is pushed to a beta branch
# For a production release, with workflow must be manually kicked off / started from Actions --> Build and Publish. This is by design to prevent accidental production releases.concurrency:

# 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 - Create a new branch including the target release version ie `beta-0.5.6`
# 2 - Update the package.json version tag to match, and push release to the `beta-0.5.6` branch. This will trigger a npm release with the beta tag, and npm version set to `0.5.6-beta.0`.
# 3 - As updates are made to the beta branch, npm beta releases will be created.
# 4 - Once the release is complete, and ready for general release, create a pull request to merge the changes into the `latest` branch.
# 5 - After reviews are complete, merge the pull request
# 6 - For the general release, the workflow must be manually kicked off / started from Actions --> Build and Publish
# 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.6`
# 3 - 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 `latest` branch.
# 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

on:
push:
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
@@ -1,6 +1,6 @@
{
"name": "bonjour-hap",
"version": "3.7.0",
"version": "3.7.1",
"description": "A Bonjour/Zeroconf implementation in pure JavaScript (for HAP)",
"main": "index.js",
"author": "Thomas Watson Steen <w@tson.dk> (https://twitter.com/wa7son)",
Expand Down