Repository navigation
release: prepare v0.0.14 - #374
Merged
Merged
Conversation
Opens the 0.0.14 section over what has landed since 0.0.13: Scoop packaging for Windows, the Linux/X11 crash fix, and CLI output appearing on Windows. Bumps the version in the five places `version:set` covers — package.json, package-lock.json (both entries), tauri.conf.json, Cargo.toml and Cargo.lock — so `shipped_version_agrees_across_every_manifest` passes and release.yml's tag/manifest guard will accept the v0.0.14 tag. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
🔍 Advisory audit reportThese checks don't block merges — they surface drift in dependencies, licensing, and external links. cargo-deny
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #374 +/- ##
=======================================
Coverage 89.71% 89.72%
=======================================
Files 148 148
Lines 25671 25671
Branches 861 861
=======================================
+ Hits 23031 23033 +2
+ Misses 2614 2612 -2
Partials 26 26
🚀 New features to boost your workflow:
|
Contributor
📖 Docs preview✅ Built and deployed for commit
Posted by docs-preview.yml — updates in place on every push. |
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.
Summary
Opens the 0.0.14 section over what has landed since 0.0.13 and bumps the version in the five places
version:setcovers, soshipped_version_agrees_across_every_manifestpasses andrelease.yml's tag/manifest guard accepts av0.0.14tag.Shipping in 0.0.14:
XInitThreadsbefore any display opens.entracteCLI output appearing on Windows (Windows CLI prints nothing: the GUI-subsystem binary never attaches to the console #364).Behind those, not user-facing: the wasmtime advisory reachability analysis (#362), the cspell worktree false-pass fix (#366), and the AppImage launcher-permission fix (#373).
Why this release matters beyond the changelog
Two first-time release paths fire on publish:
bump-scoop.ymlruns for the first time and commitsbucket/entracte.json. It only works if the release carriesEntracte_0.0.14_x64-portable.zipand that zip appears inSHA256SUMS.txt— worth confirming on the draft before publishing.The AppImage carries the launcher fix. 0.0.13 was rejected by the AppImage catalog (appimage.github.io#9123) because
AppRun.wrappedwas0770. fix(appimage): bump the Tauri CLI and guard AppDir permissions #373's CLI bump fixes it, verified on a real AppImage build:So
/reteston that PR should pass once 0.0.14 is published.What I ran
shipped_version_agrees_across_every_manifestpasses;format:checkandaudit:spellclean. No code changed — version strings and the changelog heading only.🤖 Generated with Claude Code