8000 chore: release main by release-please[bot] · Pull Request #5696 · googleapis/repo-automation-bots · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: release main #5696

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

Merged
merged 1 commit into from
Mar 12, 2025
Merged

chore: release main #5696

merged 1 commit into from
Mar 12, 2025

Conversation

release-please[bot]
Copy link
Contributor

🤖 I have created a release beep boop

bot-config-utils: 9.0.0

9.0.0 (2025-03-12)

⚠ BREAKING CHANGES

  • deps: update gcf-utils to v17 (#5695)

Bug Fixes

issue-utils: 5.0.0

5.0.0 (2025-03-12)

⚠ BREAKING CHANGES

  • deps: update gcf-utils to v17 (#5695)

Bug Fixes

object-selector: 6.0.0

6.0.0 (2025-03-12)

⚠ BREAKING CHANGES

  • deps: update gcf-utils to v17 (#5695)

Bug Fixes

datastore-lock: 7.0.0

7.0.0 (2025-03-12)

⚠ BREAKING CHANGES

  • deps: update gcf-utils to v17 (#5695)

Bug Fixes


This PR was generated with Release Please. See documentation.

@release-please release-please bot requested a review from a team as a code owner March 12, 2025 15:46
@dpebot
Copy link
Collaborator
dpebot commented Mar 12, 2025

/gcbrun

@chingor13 chingor13 merged commit e959aa2 into main Mar 12, 2025
22 checks passed
@chingor13 chingor13 deleted the release-please--branches--main branch March 12, 2025 15:54
Copy link
Contributor Author

Copy link

Triggered job: cloud-devrel/client-libraries/nodejs/release/googleapis/repo-automation-bots/publish (2025-03-12T15:54:48.811Z)

To trigger again, remove the autorelease: triggered label (in a few minutes).

The release build has started, the log can be viewed here. 🌻

🥚 You hatched a release! The release build finished successfully! 💜

suztomo added a commit that referenced this pull request May 2, 2025
This repository creates multiple Git tags upon one release pull request (commit). Example: #5696

To adopt the new release pipeline based on Git tags, this `tagPullRequestNumber` creates an additional `release-please-<pr number>` tag to a release. We'll monitor that tag to trigger the release job. This doesn't change existing release tags.

Background: https://docs.google.com/document/d/1Y0Fv-sxLqYmjnXHry3WDq4XNPeQP1AEmsB83hNRCEY0/edit?usp=sharing&resourcekey=0-I2m8Z-mTD0-HY0TpkblOTQ

This design has been working good for google-cloud-go: https://github.com/googleapis/google-cloud-go/blob/main/.github/release-please.yml#L4
suztomo added a commit that referenced this pull request May 5, 2025
This repository creates multiple Git tags upon one release pull request
(commit). Example:
#5696

To adopt the new release pipeline based on Git tags, this
`tagPullRequestNumber` creates an additional `release-please-<pr
number>` tag to a release. We'll monitor that tag to trigger the release
job. This doesn't change existing release tags.

Background:
https://docs.google.com/document/d/1Y0Fv-sxLqYmjnXHry3WDq4XNPeQP1AEmsB83hNRCEY0/edit?usp=sharing&resourcekey=0-I2m8Z-mTD0-HY0TpkblOTQ

This design has been working good for google-cloud-go:
https://github.com/googleapis/google-cloud-go/blob/main/.github/release-please.yml#L4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0