Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(migration): Do not touch release-please-manifest.json #11113

Merged
merged 3 commits into from
Apr 20, 2023

Conversation

vchudnov-g
Copy link
Contributor

No description provided.

@vchudnov-g vchudnov-g requested a review from parthea April 20, 2023 18:04
@vchudnov-g vchudnov-g requested a review from a team as a code owner April 20, 2023 18:04
@parthea parthea changed the title fix(migration): Do not touch release-please-manifest.json chore(migration): Do not touch release-please-manifest.json Apr 20, 2023
@parthea parthea added the owlbot:run Add this label to trigger the Owlbot post processor. label Apr 20, 2023
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Apr 20, 2023
@parthea parthea enabled auto-merge (squash) April 20, 2023 18:14
@parthea parthea added the owlbot:run Add this label to trigger the Owlbot post processor. label Apr 20, 2023
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Apr 20, 2023
@parthea parthea merged commit 32756dd into googleapis:main Apr 20, 2023
vchudnov-g added a commit to vchudnov-g/google-cloud-python that referenced this pull request Apr 21, 2023
…manifest

We actually do still need to copy the release-please-manifest.json
value from the split reopm, since that contains the real version
number last released. Relying on the owl-bot generated version would
reset the version numbering.
vchudnov-g added a commit to vchudnov-g/google-cloud-python that referenced this pull request Apr 21, 2023
…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.
parthea pushed a commit that referenced this pull request Apr 21, 2023
…11124)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants