Repository navigation
fix(sync): sync the CLI's renamed v0.x and v1.x branches - #22
Merged
Merged
Conversation
nborges-aws
approved these changes
Nov 10, 2026
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.
Problem
aws/agentcore-clirenamedmaintov0.xandrefactortov1.x. The CLI case inreusable-sync-from-public.ymlstill listsmain preview.sync_branchchecks each branch withgit ls-remote --heads, which doesn't follow GitHub's rename redirect, so it finds neither branch on the public repo, skips both, and the run still reports success. The CLI's private copy has received no public commits since the rename.Change
The CLI case now syncs
v0.x v1.x. The other cases (SDK Python, SDK TypeScript, and the fallback) are unchanged and still syncmain, which their public repos still have.Callers pin this workflow by SHA, so nothing changes for any repo until it bumps its pin. Only the CLI caller needs to bump for this fix.