release: 0.7.1-rc.1 - #59
Merged
Merged
Conversation
The updates were all chore/ci commits, which CONTRIBUTING reserves from the changelog, so Development stood empty. It cannot stay that way through a release: bump-version promotes that section verbatim and release-notes.mjs exits non-zero on an empty one, which would fail the publish job after all six matrix legs had already built and signed. The bullet is also true on its own terms. A patch release whose entire content is a dependency refresh should say so, and say what did not change with it.
The Version column of LICENSE's Third-Party Notices table names what a release actually ships, and today's updates left nine rows behind: aes, argon2, interprocess, toml, uuid and the two tauri plugins on the cargo side, plus motion and the clipboard plugin on the npm side. Only the versions moved. Every one of these is still MIT OR Apache-2.0, 0BSD OR Apache-2.0, or plain MIT, so the licence and copyright columns are unchanged and nothing about the policy check changed with them. Checked the whole direct set rather than only the rows that moved: 30 direct cargo dependencies and 8 npm production dependencies, none carrying a licence on CONTRIBUTING's disallowed list.
lorem-dev
force-pushed
the
release/0.7.1-rc.1
branch
from
September 8, 2026 21:48
f0ade68 to
6e11b48
Compare
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.
Release commit for the first release candidate this repository has cut. Its purpose is to exercise
release.ymlagainst the action majors that landed today and that no pull request can reach.Three commits
docs: record the dependency refresh in the changelog-- everything merged today wasci:orchore:, which CONTRIBUTING reserves from the changelog, so## Developmentstood empty. That could not survive a release:bump-versionpromotes the section verbatim, andrelease-notes.mjsexits non-zero on an empty one. The failure would have landed in thepublishjob after all six matrix legs had built and signed.chore: refresh the third-party notices versions-- from running thecheck-licensesgate. The Version column ofLICENSE's Third-Party Notices table names what a release actually ships, and today's updates left nine rows behind (aes,argon2,interprocess,toml,uuid, both tauri plugins, plusmotionand the npm clipboard plugin). Only versions moved; every licence column is unchanged.release: 0.7.1-rc.1--node scripts/bump-version.mjs 0.7.1-rc.1, touching exactly the expected set: threepackage.json,tauri.conf.json,Cargo.toml, the five workspace members inCargo.lock, and the promotedCHANGES.mdsection.Licence check
Ran over the full direct set, not only the rows that moved:
MIT OR Apache-2.0,Apache-2.0 OR MIT, or0BSD OR Apache-2.0.MITorApache-2.0 OR MIT.Gates run locally
check-tag-branch.mjscannot run until the tag exists; it is the release pipeline's first job and will assert the RC is reachable fromdevelop.What the RC is meant to prove
tauri-apps/tauri-actionrelease.ymlis tag-onlyactions/download-artifactactions/upload-artifactAn RC publishes as a GitHub pre-release, and
releases/latest/download/...-- what both one-line installers use -- never resolves to a pre-release, so this cannot reach users.The tag is not part of this pull request. It gets cut from
developafter this merges, as a separate deliberate step.