Repository navigation
chore(migration): Revert #11113, to process release-please-manifest - #11124
Merged
Merged
Conversation
…manifest We actually do still need to copy the release-please-manifest.json value from the split repo, since that contains the real version number last released. Relying on the owl-bot generated version would reset the version numbering.
vchudnov-g
force-pushed
the
post-migration-fixes-6
branch
from
April 21, 2023 00:23
78c31fc to
5cdd71a
Compare
parthea
approved these changes
Apr 21, 2023
parthea
enabled auto-merge (squash)
April 21, 2023 00:42
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.
We actually do still need to copy the release-please-manifest.json value from the split repo, since that contains the real version number last released. Relying on the owl-bot generated version would reset the version numbering.