chore: refresh cross-repo pins to post-activation main heads - #38
Merged
Conversation
Update .github/cross-repo-pins.json so data-connect and pdpp both pin to their current main head (post-activation-PR merge, both now with consumer_pin_required: true) and branch fields -> main, now that the coordinated cutover is live. Also remove the temporary move-a-polyfill-connectors push trigger from cross-repo-integrity.yml's push.branches list: that branch merged as #36, so the workflow only needs to run on pushes to main. The pull_request, schedule, and workflow_dispatch triggers are unchanged. Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
Schema Health Check — All ClearAll 63 scopes have consistent local schema files. |
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
1 participant
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.
Updates
.github/cross-repo-pins.jsonso both producer pins point at their post-activation main heads, now that the coordinated cutover is live:data-connect:b31bf312(PR chore(deps): bump the npm group across 1 directory with 3 updates #26 head) ->9ef24d46(main, merge commit of activation PR docs: clarify published PDPP artifact status #29 — flipsconsumer_pin_requiredtotrue)pdpp:dc5c878e(PR #155 head) ->a0924e9a(main, merge commit of activation PR #170 — flipsconsumer_pin_requiredtotrue)Both
branchfields move from a topic branch tomain.Also removes the temporary
move-a-polyfill-connectorspush trigger from.github/workflows/cross-repo-integrity.yml'spush.brancheslist — that branch merged as #36, so per the workflow's own comment this entry is now dead weight. Thepull_request,schedule, andworkflow_dispatchtriggers are untouched.This pin change triggers the real cross-repo integrity jobs against the live post-cutover heads — the merge of this PR is the Row 12 proof.