Skip to content

Commit

Permalink
chore(main): release protocol 1.6.1
Browse files Browse the repository at this point in the history
  • Loading branch information
taiko-kitty committed Jun 10, 2024
1 parent 37cb7af commit 970b41d
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .release-please-manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
"packages/fork-diff": "0.6.0",
"packages/guardian-prover-health-check": "0.1.0",
"packages/guardian-prover-health-check-ui": "0.1.0",
"packages/protocol": "1.6.0",
"packages/protocol": "1.6.1",
"packages/relayer": "0.12.0",
"packages/taiko-client": "0.26.0",
"packages/nfts": "1.0.0",
Expand Down
8 changes: 8 additions & 0 deletions packages/protocol/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog

## [1.6.1](https://github.com/taikoxyz/taiko-mono/compare/protocol-v1.6.0...protocol-v1.6.1) (2024-06-10)


### Bug Fixes

* **protocol:** fix an issue for `ProverSet.proposeBlock` ([#17521](https://github.com/taikoxyz/taiko-mono/issues/17521)) ([d3037ad](https://github.com/taikoxyz/taiko-mono/commit/d3037ad6551b5ae6353a360ae3677ec17cd00ec9))
* **protocol:** fix ProverSet permission issue ([#17527](https://github.com/taikoxyz/taiko-mono/issues/17527)) ([98b47d4](https://github.com/taikoxyz/taiko-mono/commit/98b47d421697694db1926486410c08adbf4a6155))

## [1.6.0](https://github.com/taikoxyz/taiko-mono/compare/protocol-v1.5.0...protocol-v1.6.0) (2024-06-07)


Expand Down
2 changes: 1 addition & 1 deletion packages/protocol/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@taiko/protocol",
"version": "1.6.0",
"version": "1.6.1",
"private": true,
"scripts": {
"buildMerkle": "ts-node ./utils/airdrop/buildMerkleTree.ts ./utils/airdrop/airdrop_db/example_claimList.json",
Expand Down

0 comments on commit 970b41d

Please sign in to comment.