fix: prevent concurrent update-extension-list push failures#340
Merged
fix: prevent concurrent update-extension-list push failures#340
Conversation
Add job-level concurrency group to serialize update-extension-list runs, and add git pull --rebase before push as a safety net. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jonkeane
approved these changes
Apr 15, 2026
Collaborator
jonkeane
left a comment
jonkeane
left a comment
There was a problem hiding this comment.
Thanks for this! I meant to come back to this and fix this, but got distracted elsewhere
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
2 participants
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.
Summary
concurrencygroup to theupdate-extension-listjob so only one instance runs at a time (others queue instead of cancelling)git pull --rebasebeforegit pushas a safety net in case local main is behind remoteFixes the race condition where merging multiple extension PRs in quick succession causes the second workflow run's push to be rejected (e.g. this run).