Repository navigation
upgrade: raise named dependencies in CI and off a topic - #7
Merged
Merged
Conversation
A raise with named directories needs no topic and no store: it edits the root's config on any branch, and in CI, which keeps no store, it reads the newest version tag from the remote by name, the way a sourceless dependency's registry is read. Promotion keeps both rules. This lets a scheduled job keep a workspace's pins current. Claude-Session: https://claude.ai/code/session_01SyPUUhGj8Msg753dGmguxq
… rule The CI path read every ref the remote advertised and picked the newest version by name, so a branch named like a version, or a tag cut on a line the repository does not pin, could be written in as a pin. It now fetches the repository's history alone — commits, branches and tags, no files — into a store made for the command and applies the same candidates rule a developer machine does. Claude-Session: https://claude.ai/code/session_018fr6kum7myDDnc3cmS6TfH
# Conflicts: # docs/test-catalog.md
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.
git upgrade <dir>raised a dependency only on a topic and only on a developer machine, so a scheduled CI job that keeps a workspace's pins current could do neither.git upgradewith no directories) still needs a topic and still refuses in CI, now pointing at the raise.--filter=tree:0: commits, branches and tags, no files) into a store made for the command and removed after it, and applies the same rule as a developer machine: tags only, reachable from a branch the repository pins, holding the pin. A branch named like a version, or a tag on an unpinned hotfix line, is never taken.Tests:
normal_032raises a calendar pin in CI with no topic, in its major and skipping a pre-release;normal_033checks the release rule in CI;error_020/error_021updated.Every open PR regenerates
docs/test-catalog.md: whichever merges later rerunsGITSCALE_UPDATE_CATALOG=1 cargo test --test it catalog::after rebasing. With #5 merged too, a CI raise of a lazy dependency that is not placed works.https://claude.ai/code/session_018fr6kum7myDDnc3cmS6TfH