0.1.1: the beam_mcp requirement is ~> 0.7; CHANGELOG headings [0.1.0] and [0.1.1] - #2
Merged
Merged
Conversation
…s), and the CHANGELOG carries its headings. 0.1.0's ~> 0.7.0 held a host on core 0.7.x, so {:beam_mcp, "~> 0.8.0"} beside {:beam_mcp_signer, "~> 0.1.0"} did not resolve once core's 0.8.0 shipped (the release lane measured it; core's UPGRADING says so). Core's public surface is frozen from 0.7.0 to 1.0.0 by its own rule and this package uses nothing outside the BeamMCP.Signer behaviour and Canonical.signature/3's bytes, so the requirement spans 0.7, 0.8 and any 0.9 and stops at 1.0.0. mix.lock resolves beam_mcp 0.8.0 at outer checksum b5a1beba2c936c2c50e164c43240ac31bc8b159a994980083ec0f6562392801e, the bytes hex.pm serves and the provenance run attested. CHANGELOG: [0.1.0] -- 2026-09-19 (published with the heading still reading Unreleased; that tarball cannot be fixed) and [0.1.1] -- 2026-09-19. No code change: 10 tests, 0 failures against core 0.8.0; the planted System.get_env fallback for the key is still red (10 tests, 4 failures) and restored
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.
0.1.0's
~> 0.7.0held a host on core 0.7.x, so the pair did not resolve once beam_mcp 0.8.0 shipped. The requirement is~> 0.7now — core's public surface is frozen from 0.7.0 to 1.0.0 by its own rule, and this package uses nothing outside the behaviour and the canonical bytes. mix.lock resolves beam_mcp 0.8.0 at outer checksum b5a1beba…801e. CHANGELOG headings[0.1.0]and[0.1.1]. No code change: 10 tests, 0 failures against 0.8.0; the planted env read still red (10/4). Not published.