Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces 3 GitHub Actions workflows:
create-tag.yml- A reusable workflow that can be invoked directly via dispatch (uncommon, usually for testing in isolation), or called by another workflow (common). This creates a tag on a specific git ref.create-release.yml- A reusable workflow that can be invoked directly via dispatch (uncommon, usually for testing in isolation), or called by another workflow (common). This creates a release based on a given tag.generate-tag-release.yml- A workflow that can be manually invoked to generate a version number, create a tag with the version number, and publish a release. In the future, this could be triggered via workflow call during deployments.This PR also introduces 2 shell scripts to help with versioning:
gen-ver.sh- Generates a calendar version number (e.g.v25.05.21) based on the current date and any existing tagsinc-patch-ver.sh- Called withingen-ver.shto either increment or add a patch version (in case there are multiple releases on the same calendar day).Calendar Versioning
The versioning scheme introduced here uses zero-padded two-digit calendar versioning. For example, the first release on August 9, 2025 would be version
v25.08.09.To disambiguate multiple releases on the same calendar day, we add a patch version to the end. Versions without the patch component have an implicit
.0patch version. For example, the second release on August 9, 2025 would be versionv25.08.09.1.