-
Notifications
You must be signed in to change notification settings - Fork 16
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(main): release google-cloud-common 1.7.0 #318
Merged
gcf-merge-on-green
merged 1 commit into
main
from
release-please--branches--main--components--google-cloud-common
Jun 11, 2024
Merged
chore(main): release google-cloud-common 1.7.0 #318
gcf-merge-on-green
merged 1 commit into
main
from
release-please--branches--main--components--google-cloud-common
Jun 11, 2024
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
trusted-contributions-gcf
bot
added
the
kokoro:force-run
Add this label to force Kokoro to re-run the tests.
label
Jun 11, 2024
dazuma
approved these changes
Jun 11, 2024
release-please
bot
force-pushed
the
release-please--branches--main--components--google-cloud-common
branch
from
June 11, 2024 23:28
2f19674
to
d0c1373
Compare
dazuma
added
the
automerge: exact
Summon MOG for automerging, but approvals need to be against the latest commit
label
Jun 11, 2024
release-please
bot
force-pushed
the
release-please--branches--main--components--google-cloud-common
branch
2 times, most recently
from
June 11, 2024 23:36
f187d17
to
f378645
Compare
release-please
bot
force-pushed
the
release-please--branches--main--components--google-cloud-common
branch
from
June 11, 2024 23:40
f378645
to
fead551
Compare
gcf-merge-on-green
bot
deleted the
release-please--branches--main--components--google-cloud-common
branch
June 11, 2024 23:44
gcf-merge-on-green
bot
removed
the
automerge: exact
Summon MOG for automerging, but approvals need to be against the latest commit
label
Jun 11, 2024
🤖 Created releases: |
Triggered job: cloud-devrel/client-libraries/common-protos-ruby/release (2024-06-11T23:44:44.698Z) 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! 💜 |
release-tool-publish-reporter
bot
added
autorelease: published
and removed
autorelease: tagged
labels
Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
🤖 I have created a release beep boop
1.7.0 (2024-06-11)
Features
This PR was generated with Release Please. See documentation.