Skip to content

stale landing plans do not block bundle sync (knit) - #235

Merged
marc-merino merged 2 commits into
mainfrom
knit/stale-landing-plans-do-not-block-bundle-sync
Oct 1, 2026
Merged

marc-merino merged 2 commits into
mainfrom
knit/stale-landing-plans-do-not-block-bundle-sync

Conversation

@marc-merino

@marc-merino marc-merino commented Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Knit Bundle

View bundle

This PR is part of Knit bundle stale-landing-plans-do-not-block-bundle-sync.

See the other review objects in this bundle:

Bundle id: stale-landing-plans-do-not-block-bundle-sync
Bundle title: stale landing plans do not block bundle sync

A landing plan generated before the bundle's latest commits pins old
heads, and the sync remote refuses it as a stale bundle fingerprint.
Uploading it failed the whole bundle sync with an HTTP 422 that did not
mention the plan, even though the artifact had already been pushed.

Sync now keeps such a plan local and says how to regenerate it, and a
landing plan upload that still fails is reported as a warning after the
artifact and history sync instead of as a skipped sync.

Knit-Group: kg_20261001_6de23a
Knit-Bundle: stale-landing-plans-do-not-block-bundle-sync
Knit-Group: kg_20261001_a56443
Knit-Bundle: stale-landing-plans-do-not-block-bundle-sync
@marc-merino
marc-merino merged commit f8accfc into main Oct 1, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant