Repository navigation
Release flow: how to pin Frame, and a consumer CI builds - #29
Merged
Merged
Conversation
fts-forge
Bot
force-pushed
the
chore/gh-6-release-flow
branch
from
November 2, 2026 05:48
6ae8599 to
1cbd621
Compare
fts-forge
Bot
force-pushed
the
refactor/gh-5-core-architect-split
branch
from
November 2, 2026 05:50
300936a to
8c541c7
Compare
fts-forge
Bot
force-pushed
the
chore/gh-6-release-flow
branch
from
November 2, 2026 06:01
1cbd621 to
427ebca
Compare
fts-forge
Bot
changed the base branch from
refactor/gh-5-core-architect-split
to
main
November 2, 2026 06:17
- README: Using Frame (the tag snippet, the [patch] tables to repeat, the lock to start from) and Releases (semver vX.Y.Z on a green main; moving with architect through architect's `just fleet-bump vX.Y.Z ../frame`). - examples/consumer: the snippet as an out-of-tree crate (its own workspace), pinned by tag v0.1.0. `just consumer` (a CI job) builds it against the commit under test by patching Frame's git source to this checkout, so it works before the tag exists and without repo access, and fails when its [patch] tables drift from Frame's. - It starts from Frame's Cargo.lock: a fresh resolve picked smallvec 2.0 beta.4, which facet-styx 5.0.0-rc.7 doesn't compile against.
…kout Patching the consumer's Frame git source still made cargo fetch the repo, which the pool runner can't read (private, no credentials) and which has no v0.1.0 tag yet. The check now builds a scratch copy whose frame and frame-architect dependencies are path deps on the checkout.
fts-forge
Bot
force-pushed
the
chore/gh-6-release-flow
branch
from
November 2, 2026 06:17
427ebca to
5440750
Compare
2 tasks
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
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.
Part of #6 (it closes once
v0.1.0is tagged). Part of #2. Stacked on #28 → #27 → #26; this PR's base is #28's branch.What
frame(core) andframe-architect;[patch]tables a consumer has to repeat;Cargo.lockfrom Frame's.vX.Y.Ztags on a greenmain, trunk-based, no release branches or commits;just fleet-bump vX.Y.Z ../frame, plus that tag's other pins and[patch]tables in the same PR.fleet-bumpalready takes any consumer path, so Frame needs no code entry in architect.examples/consumer: the snippet as an out-of-tree crate, in its own workspace, pinned by tagv0.1.0.just consumer, a new CI job required byci:[patch]table drifts from Frame's.smallvec2.0.0-beta.4, andfacet-styx5.0.0-rc.7 doesn't compile against it. The consumer therefore starts from Frame's lock, and the README says to.Proposed:
v0.1.0Once #26, #27, #28 and this PR are merged and
main's checks are green, tag that commitv0.1.0. Nothing is tagged yet. After the tag:Checks (local, per LOCAL-CHECKS.md)
cargo fmt --all -- --check, plus rustfmt on the consumer;just consumer, which passes.