chore(main): release 1.0.0#6
Merged
Merged
Conversation
Collaborator
|
Should we approve? In my builds I just used release tags (a tag condition in the build.yaml) to indicate build AND release but here we have two build files. ? |
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
af7abb9 to
7885459
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
7885459 to
d19d9d1
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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
1 participant
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.0.0 (2026-07-01)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.