chore(release): prepare 0.1.19 - #78
Merged
Merged
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
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.
What changed
Set
package.jsonto 0.1.19 after OpenCode Go session support merged through #76. The macOS packager requires the package version to matchRELEASE_VERSION, so this gives the next signed preview a distinct version and immutable archive name.Verification
git diff --checkpassed. This PR's aggregate CI will qualify the versioneddevelopmenttree before merge.Security review
This changes only the display version in
package.json. Authentication, dependencies, workflows, signing keys, feed generation, and release distribution code are unchanged. The release will use the existing external Sparkle key, a build number above the published inventory, clean-source packaging, and signed feed/archive verification before publication.