-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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 protocol 1.9.0 #18052
Merged
dantaik
merged 2 commits into
main
from
release-please--branches--main--components--protocol
Sep 12, 2024
Merged
chore(main): release protocol 1.9.0 #18052
dantaik
merged 2 commits into
main
from
release-please--branches--main--components--protocol
Sep 12, 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
taiko-kitty
force-pushed
the
release-please--branches--main--components--protocol
branch
from
September 10, 2024 00:08
af5024c
to
77a22c2
Compare
taiko-kitty
force-pushed
the
release-please--branches--main--components--protocol
branch
from
September 11, 2024 04:43
77a22c2
to
a7a1535
Compare
taiko-kitty
changed the title
chore(main): release protocol 1.10.0
chore(main): release protocol 1.9.0
Sep 12, 2024
taiko-kitty
force-pushed
the
release-please--branches--main--components--protocol
branch
from
September 12, 2024 00:07
a7a1535
to
3ebfa19
Compare
dantaik
approved these changes
Sep 12, 2024
YoGhurt111
approved these changes
Sep 12, 2024
dantaik
deleted the
release-please--branches--main--components--protocol
branch
September 12, 2024 00:43
🤖 Created releases: |
This was referenced Dec 27, 2024
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
1.9.0 (2024-09-12)
Features
DevnetTaikoL1
(#17900) (d864cea)proveBlocks
method toProverSet
(#18025) (36a2ae5)proveBlocks
to TaikoL1.sol (fe687b3)TIER_ZKVM_RISC0
tier andHeklaTierProvider
(#17913) (64ed666)UpgradeRisc0Verifier
(#17949) (fc12e04)HeklaTierProvider
to introduce sp1 proof (#18022) (76b6514)ontakeForkHeight
to Sep 24, 2024 (#18046) (30c9316)ontakeForkHeight
(#17983) (8819e3a)Bug Fixes
chainId
inHeklaTaikoL1
(#17912) (8f31dd0)basefeeSharingPctg
(#17889) (5f3cbc9)Chores
adjustExcess
(#17891) (ba21f68)TAIKO_TOKEN
name changes inDeployOnL1
(#17927) (cf1a15f)Documentation
DelegateOwner
address in Hekla deployment docs (#17925) (fdec8db)tier_router
with compatibility modifications (#18028) (c43cb0c)tier_router
(#18023) (11e27d6)Code Refactoring
livenessBond
,proposedAt
, andproposedIn
to storage (17d67d7)Tests
Workflow
Build
This PR was generated with Release Please. See documentation.