-
Notifications
You must be signed in to change notification settings - Fork 22
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 did-mailto 2.1.0 #1114
Open
it-dag-house
wants to merge
1
commit into
main
Choose a base branch
from
release-please--branches--main--components--did-mailto
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 did-mailto 2.1.0 #1114
it-dag-house
wants to merge
1
commit into
main
from
release-please--branches--main--components--did-mailto
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
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
7 times, most recently
from
November 20, 2023 11:17
609a4a2
to
8ad9cbb
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
5 times, most recently
from
November 27, 2023 12:05
2196666
to
45b60ba
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
6 times, most recently
from
December 4, 2023 19:45
3c7b433
to
901b878
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
3 times, most recently
from
December 7, 2023 09:51
3bc9e0e
to
9233227
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
2 times, most recently
from
December 14, 2023 19:06
310cd1d
to
3b12641
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
from
January 3, 2024 17:39
3b12641
to
ba49680
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
4 times, most recently
from
January 18, 2024 10:54
d444c80
to
2cf1097
Compare
it-dag-house
force-pushed
the
release-please--branches--main--components--did-mailto
branch
from
January 24, 2024 16:13
2cf1097
to
f20e48a
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
from
July 29, 2024 11:08
de3c37a
to
f6a8cc7
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
from
August 30, 2024 19:04
f6a8cc7
to
135a792
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
4 times, most recently
from
September 23, 2024 09:15
5c01036
to
1fc8a97
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
4 times, most recently
from
October 14, 2024 18:06
6d9a966
to
82f1d24
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
3 times, most recently
from
October 24, 2024 13:32
a8db1ab
to
79599aa
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
2 times, most recently
from
November 5, 2024 19:49
cdfa8ca
to
86ceb2f
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
4 times, most recently
from
November 22, 2024 20:33
21f8aed
to
c9933ba
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
4 times, most recently
from
November 29, 2024 09:39
e63c024
to
1a8c268
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
3 times, most recently
from
December 9, 2024 15:31
82cb05f
to
dd1e22b
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
2 times, most recently
from
December 19, 2024 13:48
f48e9d3
to
dba3d57
Compare
github-actions
bot
force-pushed
the
release-please--branches--main--components--did-mailto
branch
from
December 20, 2024 12:43
dba3d57
to
1577556
Compare
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
2.1.0 (2024-12-20)
Features
Fixes
Other Changes
pnpm dev
to watch-build all packages (#1533) (07970ef)This PR was generated with Release Please. See documentation.