Repository navigation
Add SemVer machinery. - #26
Merged
Merged
Conversation
The Swift Server ecosystem has machinery for making sure that SemVer is used for changes and reflected easily and correctly in releases. This PR adopts those tools so that we can more easily ensure we don't break downstream consumers of the package. * Add PR workflow check for SemVer labels * Add `release.yml` which will allow GitHub's release/tag flow to automatically group merged changes by SemVer level.
rnro
requested review from
agnosticdev,
baumanl,
ekinnear,
kpodosin and
tfpauly
as code owners
October 5, 2026 20:33
tfpauly
approved these changes
Oct 5, 2026
kpodosin
approved these changes
Oct 5, 2026
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
3 participants
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.
The Swift Server ecosystem has machinery for making sure that SemVer is used for changes and reflected easily and correctly in releases. This PR adopts those tools so that we can more easily ensure we don't break downstream consumers of the package.
release.ymlwhich will allow GitHub's release/tag flow to automatically group merged changes by SemVer level.