Repository navigation
Conversation
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.
The first
syncinto a fresh Linear pipeline scans only the current commit: the CLI bounds the range by the pipeline's last release, and a new pipeline has none. app-backend's first mirrored release, v0.41.0 in the new "App back-end" pipeline, landed with zero issues that way while the PR summary listed six tickets (APP-1079).steps/linear-releasetakes an optionalbase-ref(forwarded as the CLI's--base-ref, sync only) andrelease-startpasses the latest<tag-prefix>*tag — the same boundary the summary and the stale-version guard use — so the mirror no longer depends on what the pipeline remembers and every new pipeline starts linked in full. Backfilling v0.41.0 itself is a one-offsync --base-ref=v0.40.1 --release-version=v0.41.0with the pipeline key.🤖 Generated with Claude Code