chore(main): release Google.Cloud.EntityFrameworkCore.Spanner 3.0.0 #450
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
![release-please[bot]](https://avatars.githubusercontent.com/in/40688?s=60&v=4){kind=small}
trusted-contributions-gcf
bot
added
the
kokoro:force-run
release-please
bot
changed the title
release-please
bot
force-pushed
the
release-please--branches--main--components--Google.Cloud.EntityFrameworkCore.Spanner
branch
4 times, most recently
from
9a31b4c
to
0956b30
Compare
release-please
bot
force-pushed
the
release-please--branches--main--components--Google.Cloud.EntityFrameworkCore.Spanner
branch
from
0956b30
to
9f1b99c
Compare
…Google.Cloud.EntityFrameworkCore.Spanner
olavloite
approved these changes
Oct 10, 2024
olavloite
deleted the
release-please--branches--main--components--Google.Cloud.EntityFrameworkCore.Spanner
branch
|
🤖 Created releases: 🌻 |
|
Triggered job: cloud-sharp/dotnet-spanner-entity-framework/gcp_windows/autorelease (2024-10-10T22:46:28.529Z) To trigger again, remove the autorelease: triggered label (in a few minutes). |
|
The release build has started; the log can be viewed here. |
|
The release build failed! Please investigate! |
release-tool-publish-reporter
bot
added
autorelease: failed
and removed
autorelease: tagged
labels
amanda-tarafa
added
autorelease: tagged
and removed
autorelease: failed
autorelease: triggered
labels
|
The release build has started; the log can be viewed here. |
|
The release build failed! Please investigate! |
release-tool-publish-reporter
bot
added
autorelease: failed
and removed
autorelease: tagged
labels
|
@olavloite I'm on this |
|
The release build has started; the log can be viewed here. |
|
The release build failed! Please investigate! |
amanda-tarafa
added
autorelease: tagged
and removed
autorelease: failed
autorelease: triggered
labels
|
The release build has started; the log can be viewed here. |
|
The release build failed! Please investigate! |
release-tool-publish-reporter
bot
added
autorelease: failed
and removed
autorelease: tagged
labels
|
I'm still testing on this, we'll see a few failures. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
3.0.0 (2024-10-10)
⚠ BREAKING CHANGES
Features
This PR was generated with Release Please. See documentation.