Repository navigation
Release v1.3.0 and publish desktop update manifest - #1264
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying mouseterm with
|
| Latest commit: |
6a0bbaa
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4fea6f37.mouseterm.pages.dev |
| Branch Preview URL: | https://release-next.mouseterm.pages.dev |
dormouse-bot
approved these changes
Oct 21, 2026
# Conflicts: # scripts/spec-word-budgets.json
dormouse-bot
approved these changes
Oct 21, 2026
nedtwigg
had a problem deploying
to
hosted-preview
October 21, 2026 00:51 — with 
GitHub Actions
Error
GitHub Actions
Error
This branch was successfully deployed
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.
Publishes the v1.3.0 release notes and synchronized desktop/extension versions, together with the signed desktop update manifest. The website's download buttons and the Tauri updater point at the three published v1.3.0 assets once this reaches the production
releasebranch.CHANGELOG.md: the 1.3.0 section, covering the merges since v1.2.0.tauri.conf.json,Cargo.toml/Cargo.lock,vscode-ext/package.json, andlib/package.json.website/public/standalone-latest.json: v1.3.0 URLs and signatures for macOS, Windows, and Linux.Start every release on its own branch and merge it with a merge commit(deploy.md and the release-notes command) and the release website snapshot refresh.Merge with a merge commit, never a squash, so the
v1.3.0tag (at21be333) stays inmain's history for the build stamp.Validation:
v1.3.0succeeded: all three standalone builds, the VS Code extension build, and Publish VSCode Extension. The security-audit gate passed on a rerun; the first attempt was INCONCLUSIVE only because one audit agent wrote a result line for a rule it does not own (S29).v1.3.0is published with exactly the three assets the manifest names.🤖 Generated with Claude Code