Support --version Option + CI
#7
Merged
Conversation
This file contains 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
Base automatically changed from
refactor/release-prep/3-ci
to
refactor/release-prep/0-main
December 4, 2023 16:10
jagreenwood
approved these changes
Dec 4, 2023
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.
Adds support for the
--versionoption and CI support for maintaining this. My basic thought is that any development tool should accurately report its version to help users deal with breaking changes and maintenance of this should be automated.This adds our swift-version-file-plugin Swift Package Manager command plugin as a dependency and uses that to maintain a
Version.swiftfile supplying the value forWatcher.configuration.version.It also adds a
Prepare Releaseworkflow to create a new PR for an updated version file on areleasebranch and aTag Releaseworkflow to create a new tag corresponding toVersion.numberwhen that PR is closed.Finally, this adds a
RELEASEdocument to explain this process and its motivation for future maintainers.NOTE: I have tested this setup successfully on a personal repo and believe it should be compatible with this one's current settings, though some additional token management could be required.