Record dependency refresh and coordinated release rollout - #4
Merged
Merged
Conversation
terjekv
marked this pull request as ready for review
September 19, 2026 13:41
terjekv
changed the title
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.
Record the completed dependency refresh across all ten Treetop repositories, with merged PR links, dependency-aware squash order, prerequisite release order, archive migration steps, Rust/Node requirements, and the explicit TypeScript compatibility holdback. Link the record from the repository README, organization profile, and previous coordinated migration guide.
The organization repository has no package dependencies to upgrade. Its GitHub Actions and pinned Markdown tooling were checked against current upstream releases and are already current. Preserve those verified pins without artificial version changes.
The rollout record distinguishes published packages from merged implementation updates that await separate versioned releases. Core and Bundle 0.2.0 are published, including every native Bundle CLI archive. REST now resolves both published registry crates, and Bundle Action uses the published CLI and its immutable release source. REST, all clients, CLI, frontend, and Bundle Action are squash-merged. They retain their existing published versions until separately released.
Validation: Markdown lint, actionlint, and every relative document/asset link. No branding assets changed.