Repository navigation
Conversation
* Simplify release promotion and version-derived documentation * Require a version tag for dispatched binary publication * Format release validation and smoke checks
mveril
force-pushed
the
chore/start-beta-2-development
branch
from
November 12, 2026 18:50
828c2e6 to
1686c35
Compare
This branch has not been 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.
Port the two release-only changes from main onto develop and resume development at
0.1.0-beta.2.dev. This replaces #216 with three focused commits, avoiding the nine patch-equivalent commits from main's separate history.Prepare release v0.1.0-beta.1andHarden release metadata and archive checks.0.1.0-beta.2.dev; regenerate license notices.The final tree is byte-for-byte identical to #216. This aligns content with main without merging its divergent history. No history was rewritten or force-pushed. Main, the release tag, and existing release artifacts are unchanged. No publication workflow was dispatched. The crates.io fix remains separate in #215.
Validation: 55 targeted release tests and 13 subtests passed; distribution notice checks and
git diff --checkpassed. The previous book build passed for the identical tree. Cargo metadata confirmed synchronized versions, and release validation rejects this development version.Documentation impact: retain the existing released manual changes from main. No additional manual changes are needed for the documented
.devconvention.Leave this PR unmerged for maintainer review.