chore: Remove concurrency restriction on push-latest-release workflow
#13145
Conversation
This file contains 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
jimblanc
force-pushed
the
hot-fix/release-automation
branch
from
233af3f to
0d0873e
Compare
jimblanc
changed the title
push-latest-release workflow
jimblanc
changed the title
push-latest-release workflowpush-latest-release workflow
jimblanc
force-pushed
the
hot-fix/release-automation
branch
2 times, most recently
from
8d16377 to
16fd42e
Compare
ashwinkumar6
previously approved these changes
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
elorzafe
reviewed
Mar 19, 2024
…r, and react-native.
jimblanc
force-pushed
the
hot-fix/release-automation
branch
from
16fd42e to
b37cc16
Compare
elorzafe
approved these changes
Mar 19, 2024
ashwinkumar6
approved these changes
Mar 19, 2024
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.
Description of changes
This hot-fix removes the concurrency restriction on the
push-latest-releaseworkflow, which is causing releases to be aborted when auto-generated commits are made by CI. This is happening due to the change made in #13095 which no longer skips CI entirely for these auto-generated commits. It also reverts thePublishcommit for the most recent aborted release to prepare for the hot-fix.Issue #, if available
Description of how you validated changes
[skip release]are in fact being skipped (i.e. no risk of infinite loop)publish:releaseChecklist
yarn testpassesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.