This repository has been archived by the owner on Jul 25, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 61
chore(main): release emblem 1.0.0 #732
Open
github-actions
wants to merge
1
commit into
main
Choose a base branch
from
release-please--branches--main--components--emblem
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(main): release emblem 1.0.0 #732
github-actions
wants to merge
1
commit into
main
from
release-please--branches--main--components--emblem
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
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
6 times, most recently
from
December 16, 2022 23:53
7bc5417
to
9bfd998
Compare
grayside
suggested changes
Dec 19, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Future: The changelog here is using the release-please format instead of the GitHub format. We decided that wasn't a blocker and could be fixed over time.
- Blocker: The release notes here are a bit confusing to read: we may want to use https://github.com/googleapis/release-please#how-can-i-fix-release-notes to override text.
- Discussion: Should new features in testing or a delivery pipeline be considered: chore, testing, feature(delivery)? Currently we're mostly using feature. This loops back to point (1), where I wanted to support delivery pipeline features but wanted to make sure the context from component was really clear.
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
8 times, most recently
from
January 10, 2023 20:38
aee62d9
to
d3dbd10
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
2 times, most recently
from
January 19, 2023 20:36
af40b2a
to
8848456
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
2 times, most recently
from
January 23, 2023 21:45
4a81846
to
3ebfd1a
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
2 times, most recently
from
February 10, 2023 19:42
c8cefa1
to
3eff581
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
3 times, most recently
from
February 14, 2023 00:46
e3a77a5
to
efc23b2
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
3 times, most recently
from
March 22, 2023 00:02
623b37f
to
271d8fe
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
4 times, most recently
from
November 2, 2023 21:06
3601bf3
to
0119cf2
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
5 times, most recently
from
November 14, 2023 00:14
28bb09d
to
ed9c9c4
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
5 times, most recently
from
December 2, 2023 00:54
95f123a
to
23ec7c1
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
2 times, most recently
from
December 9, 2023 00:12
11a3402
to
a3c7520
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
from
January 12, 2024 22:50
a3c7520
to
ae647bc
Compare
github-actions
bot
changed the title
chore(main): release 0.7.0
chore(main): release emblem 1.0.0
Jan 26, 2024
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
6 times, most recently
from
February 1, 2024 23:57
2b21f79
to
d5af912
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
3 times, most recently
from
March 8, 2024 06:09
2eb43df
to
33c2112
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--emblem
branch
from
March 8, 2024 06:09
33c2112
to
36f2631
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.0.0 (2024-03-08)
⚠ BREAKING CHANGES
Features
configure_delivery.sh
(#702) (eee313f), closes #701data
element (#748) (2338f9b)Bug Fixes
This PR was generated with Release Please. See documentation.