Feature/semver pipeline - #103
Merged
Merged
Conversation
Should have happened in f48f387
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
1 participant
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.
This pull request introduces an automated workflow to ensure semantic versioning compliance for pull requests, and bumps the package version in
package.jsonto1.3.0.Versioning and release process improvements:
.github/workflows/semver.yaml) that checks if theversionfield inpackage.jsonhas been updated in pull requests targeting themainbranch. The workflow fails if the version is unchanged, helping enforce proper version bumps for every PR.versionfield inpackage.jsonfrom1.2.0to1.3.0to reflect a new release.Closes #102