chore: release 1.5.0 - #182
Merged
Merged
Conversation
The only commit since v1.4.0 is a `fix:`, so release-please proposed 1.4.1. The worktree reclamation and issue-comment changes in #180 alter how automation recovers and how it reports to GitHub, which is a minor-level change rather than a patch, so pin the version explicitly. Release-As: 1.5.0
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.
Summary
Forces the next release to be a minor rather than a patch.
The only commit on
mainsincev1.4.0is #180, which is afix:— so release-please proposed 1.4.1 in #181. #180 changes how automation recovers from stranded worktrees and how it reports status to GitHub (a single edited comment instead of one per attempt), which is behaviour-level change rather than a bug patch, so the version is pinned explicitly with aRelease-As: 1.5.0footer.This is an empty commit; it carries no code change. Once merged, release-please will update #181 to propose 1.5.0 instead of 1.4.1.
This PR does not publish anything. Publishing happens when the release PR (#181) is merged — that tags
v1.5.0, creates the GitHub release, runsnpm publish --access public, and builds the Tauri artifacts.Verification
mainis at2b75dd1withv1.4.0as the latest tag, so 1.5.0 is the correct next minor.Related Issue