Repository navigation
release: 1.2.1 - #761
Merged
Merged
release: 1.2.1#761
Conversation
Version bump across the three manifests and the two lockfile entries that record the app's own version. What 1.2.1 contains since 1.2.0: - rustls 0.23.46 for RUSTSEC-2026-0346..0349 (#759) - Tauri 2.12.3, tauri-plugin-updater 2.13.3 and tauri-plugin-shell 2.5.0 on both the npm and Rust sides (#758) - Dependency roll-ups: cargo group (#756), npm group (#755), dprint plugins (#754) - cargo audit: the zip advisories reached only through the Windows updater are accepted pending upstream, tracked in #760 (#759) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WTypK4RjzzdjoFxd3qk14g
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
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.
Version bump across the three manifests and the two lockfile entries that record the app's own version (same shape as #751).
What 1.2.1 contains since 1.2.0
After merge
Per
docs/RELEASING.md:scripts/check-release-readiness.sh --strict 1.2.1on main, push tagv1.2.1, then check that all four builds, the upload and the update manifest succeed, with one draft release and the full set of assets.Validation
check-release-readiness.sh --strict 1.2.1: all three manifests read 1.2.1. Its only failure is "not on main", which applies until this merges.Generated by Claude Code