Release 0.2.0: the private key no longer reaches an exception report - #9
Merged
Merged
Conversation
… at 0.x), and the project pages
The version (0.1.1 -> 0.2.0); the Unreleased section cut as [0.2.0] - 2026-09-23 with a paragraph
naming the fix, the addition and the upgrade (requirement ~> 0.2.0, the key passed as
fn -> key end; the beam_mcp requirement ~> 0.7 unchanged, which admits core 0.10). The sections
are reordered so the security change reads first. SECURITY's table: 0.2.x yes, 0.1.x superseded
with the reason. The two older release headings lose their em dash (' - '), as beam_mcp's do.
docs/verifying-releases.md's example tag is v0.2.0. No code change in this commit; the fix is
44c70ae. The owner tags and publishes.
Signed-off-by: Ayla Croft <aylacroft@proton.me>
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 0.2.0. It publishes the security fix merged in #4: the private key no longer reaches an exception report. It also ships the project pages added since 0.1.1.
[0.2.0] - 2026-09-23, with the fix first. SECURITY: 0.2.x is supported; 0.1.x is superseded, with the reason.beam_mcprequirement stays~> 0.7, which admits core 0.10.mix docs0 warnings; REUSE compliant.a55b3d37afaba11f434b231809aa0ec70cfd38bf2b1dda56e9a91aee901ec4d2. The same bytes on ext4 and on tmpfs.The maintainer tags and publishes after the merge, with
tools/release_tarball.sh v0.2.0 beam_mcp_signer-0.2.0.tar --publish. The published checksum must equal the one above, provided the tree is unchanged.