Applying package update to 0.71.33 ***NO_CI*** #1906
Merged
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.
TL;DR
I made an error, and now the 0.71-stable NPM package & Github branch are out of sync in package versions. This PR rectifies that.
Longer Explanation
As it turns out, with my admin privileges, I can push directly to the repos'
0.71-stable
branch. This led to this unfortunate set of events:0.71-stable
with 3770a1a, which caused the publish pipeline to run.*-stable
branch.rnbot
(the bot that publishes to NPM for us and pushes the version update back to Github) couldn't push to the branch, and the publish pipeline job succeeded in publishing to NPM, but not back to GithubResult: NPM has
0.71.33
, while our repo only has0.71.32
. We can fix this by just manually bumping the version in Github ourselves, and adding***NO_CI***
to the merged commit so that the publish pipeline doesn't run again.