Announce coordinated declared-target breaking release and project policy - #3
Merged
Merged
Conversation
terjekv
marked this pull request as ready for review
September 6, 2026 12:22
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.
Announce the coordinated breaking release across all ten Treetop repositories: exact resource-type/attribute label ownership, format 2 bundles, strict current consumer contracts, and correctness over compatibility throughout early releases.
The migration guide links the published releases, gives concrete label syntax and API updates, explains the sanitation trust boundary, and documents the prerequisite release order. Core and Bundle are consumed from crates.io, client integration uses the immutable REST release image, the frontend pins its released source, and Bundle Action v2 validates the published native CLI on all supported platforms. The project catalog includes the Go client.
Call out the intentional cold-start and Go validation costs alongside the measured hot-path results. Remove the superseded compatibility guidance and pending-release language, and point the organization profile to Bundle Action v2.
Validation: Markdown lint, local links, complete repository inventory, and published version/artifact/provenance checks across the release set.