Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(main): release relayer 0.13.0 #18427

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(main): release relayer 0.13.0 #18427

wants to merge 1 commit into from
+48 −2

Conversation

taiko-kitty
Copy link
Contributor

@taiko-kitty taiko-kitty commented Nov 4, 2024 •
edited
Loading

🤖 I have created a release beep boop

0.13.0 (2025-01-10)

Features

  • relayer: confirmations before indexing for relayer should be configurable (#18466) (1fee7bb)
  • relayer: pad if contract (#18131) (56143f0)

Bug Fixes

  • eventindexer: remove nft metadata indexing, far too slowy and bug ridden right now (#18126) (f0ab1e1)
  • relayer: extra padding for contract messages, always pad non-contracts (#18699) (a950b6c)
  • relayer: fix for profitable detection (#18134) (c2f59c3)
  • relayer: profitability changes (#18124) (10eb73c)
  • relayer: temp fix if txSender is not available for txIndex when processing events (#18513) (a0c622e)

Chores

Documentation

Tests

  • taiko-client: introduce TestTxPoolContentWithMinTip test case (#18285) (d572f4c)

Workflow

Build

  • deps: bump github.com/stretchr/testify from 1.9.0 to 1.10.0 (#18539) (79f3fab)
  • deps: bump golang.org/x/sync from 0.9.0 to 0.10.0 (#18560) (3d51970)
  • relayer: upgrade scripts and ignore abi json files (#17826) (8774a48)

This PR was generated with Release Please. See documentation.

@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 13 times, most recently from 3b8aa7e to c922eab Compare November 12, 2024 03:53
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 4 times, most recently from aacc4b6 to 82b66e5 Compare November 18, 2024 02:33
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 8 times, most recently from 2555b7a to 3522c20 Compare November 28, 2024 07:07
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 4 times, most recently from 24709c8 to 5aab4a7 Compare December 6, 2024 00:43
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 9 times, most recently from 6be61f1 to c9a5b09 Compare December 23, 2024 01:25
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 7 times, most recently from ecbe324 to 72971de Compare December 30, 2024 05:11
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 9 times, most recently from 33b3640 to 1556947 Compare January 7, 2025 02:08
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 3 times, most recently from 9a6286b to 353047b Compare January 9, 2025 06:10
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 353047b to c55d041 Compare January 10, 2025 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
autorelease: pending
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@taiko-kitty