chore(release): bastion 0.2.5 - #8
Merged
Merged
Conversation
Ships #7: the public-Bytes-API migration for march#247 (array-backed Bytes), and the capability declarations march main now enforces at typecheck, codegen ceiling, and import propagation. Needed as a RELEASE, not just a merge — same reason as 0.2.4: forgepm resolves bastion from the registry (`bastion = "0.2.4"`), so its CI still typechecks the published 0.2.4 sources and fails on exactly the errors #7 fixed. A git dep is not an alternative here: this repo is private and forgepm's CI clones git deps anonymously. Verified against march main (cbb8346e): 369 tests, 0 failures.
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.
Ships #7.
Why a release, not just the merge
Same reason as 0.2.4: forgepm resolves bastion from the registry (
bastion = "0.2.4"), so its CI typechecks the published 0.2.4 sources and fails on exactly the errors #7 fixed:A git dep is not an alternative here — this repo is private, and forgepm's CI clones git deps anonymously. That was tried and rejected with
failed to clone ... exit 128.What 0.2.5 contains
Bytes)mainnow enforces in three separate places — typecheck, the codegen ceiling check, and import propagationneeds IO.File, IO.Dir, which are not capabilities in march's lattice and never granted anythingOne line:
version = "0.2.4"→"0.2.5".Verification
369 tests, 0 failures against march
main(cbb8346e — the revision CI resolves).