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.

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 relayer 0.13.0 #15721

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 9, 2024

🤖 I have created a release beep boop

0.13.0 (2024-05-13)

Features

  • blobstorage: add health check, change regular mux for echo, filter changes (#16449) (ee1233d)
  • bridge-ui: release (#17071) (2fa3ae0)
  • eventindexer: fix down mig + regen bindings (#16563) (da5a039)
  • relayer: add indexer for MAX() in MySQL (#16077) (b079ead)
  • relayer: add indexer in MySQL (#16338) (95c9bcf)
  • relayer: add one more prometheus target for rabbitmq queue (#16539) (3e3f529)
  • relayer: add Prometheus and Grafana to docker-compose (#16500) (830b83e)
  • relayer: add quota manager, update relayer, requeue failed messages (#17001) (90944a2)
  • relayer: add the bridge software to send bridge txs (#16498) (09d79ac)
  • relayer: bridge improvement (#16752) (ac93ace)
  • relayer: document indexer with comments, fix broken crawler logic, add new metrics (#16330) (4d8d9d7)
  • relayer: enable rabbitmq metrics in prometheus in docker-compose (#16525) (89d8ece)
  • relayer: handle replacement tx underpriced (#16493) (34e7207)
  • relayer: more logs for hekla (#16841) (71f8275)
  • relayer: only publish messages with new status (#16351) (88c39d8)
  • relayer: pause the bridge when a message has been detected as not sent (#16542) (ebb9da3)
  • relayer: regen bindings, make changes for stateVars, add isMessageReceived (#16664) (66a35e2)
  • relayer: relayer small fixes + logs (#16692) (cc53a17)
  • relayer: remove subscriptions, make reorg detecting easier, filter on event loop (#16417) (e985d59)
  • relayer: rmq: add dead letter exchange, add retry capability (#16345) (3a4bbd6)
  • relayer: two-step bridge + watchdog + full merkle proof (#15669) (1039a96)
  • relayer: unprofitable queue + use txmgr (#16505) (a2aa89b)
  • relayer: useful relayer logs (#16503) (8a26758)

Bug Fixes

  • blobstorage, eventindexer, relayer: remove username and password (#16700) (35adb3d)
  • eventindexer: add disperser log, remove unused stats from previous testnets (#16938) (aec6bca)
  • relayer: add revert check back in, add gas limit to response (#16734) (324d626)
  • relayer: basefee changes (#16709) (2b4eb92)
  • relayer: change gaslimit, add in block scannign as heartbeat (#16713) (462b885)
  • relayer: cost estimation (#16707) (6baf7fd)
  • relayer: fix a panic in relayer-api (#16720) (e992ec9)
  • relayer: fix bigint conversion in decode message data (#16476) (972db87)
  • relayer: fix crawler (#16617) (4cda96c)
  • relayer: fix decodeMessageSentData (#16391) (d9dc4b6)
  • relayer: func WaitConfirmations should not wait forever for ethereum.NotFound (#16547) (5578687)
  • relayer: handle retry count manually since it's lost in translation from moving between exchanges (#16922) (13cec87)
  • relayer: handling message received events should compare message dest chain with indexer source chain (#16537) (5c84e16)
  • relayer: reconnect after notify close (#16329) (8987156)
  • relayer: remove unnecessary FindLatestBlockID (#16480) (72d74b1)
  • relayer: revert func WaitConfirmations should not wait forever for ethereum.NotFound (#16554) (6ad16f5)

Performance Improvements

  • main: use errors.New to replace fmt.Errorf with no parameters (#16777) (bb0c1ae)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--relayer branch 6 times, most recently from 1072dbe to d02a28e Compare February 14, 2024 03:10
Copy link

coderabbitai bot commented Feb 14, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

codecov bot commented Feb 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.93%. Comparing base (f53766b) to head (9696523).
Report is 495 commits behind head on main.

❗ Current head 9696523 differs from pull request most recent head d44effc. Consider uploading reports for the commit d44effc to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15721      +/-   ##
==========================================
+ Coverage   26.82%   26.93%   +0.11%     
==========================================
  Files         105      104       -1     
  Lines        6188     6140      -48     
==========================================
- Hits         1660     1654       -6     
+ Misses       4348     4306      -42     
  Partials      180      180              
Flag Coverage Δ *Carryforward flag
eventindexer 17.22% <ø> (ø) Carriedforward from a19922d
guardian-prover-health-check 36.13% <ø> (+1.32%) ⬆️ Carriedforward from a19922d
relayer 37.97% <ø> (+0.08%) ⬆️

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--relayer branch 3 times, most recently from 5221d74 to 8cb0c5e Compare February 16, 2024 15:52
@github-actions github-actions bot changed the title chore(main): release relayer 0.13.0 chore(main): release relayer 1.0.0 Feb 16, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--relayer branch 5 times, most recently from 3315d41 to d7f58ab Compare February 20, 2024 00:36
@github-actions github-actions bot changed the title chore(main): release relayer 1.0.0 chore(main): release relayer 0.13.0 Feb 20, 2024
@github-actions github-actions bot force-pushed the release-please--branches--main--components--relayer branch from d7f58ab to 0828ed0 Compare February 20, 2024 02:10
@d1onys1us d1onys1us changed the title chore(main): release relayer 0.13.0 chore(main): release redlayer 0.13.0 Feb 21, 2024
@d1onys1us d1onys1us changed the title chore(main): release redlayer 0.13.0 chore(main): release relayer 0.13.0 Feb 21, 2024
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 3 times, most recently from 6298789 to 49eed03 Compare February 24, 2024 14:51
@taiko-kitty taiko-kitty changed the title chore(main): release relayer 0.13.0 chore(main): release relayer 1.0.0 Feb 25, 2024
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 5a9364a to b8e0457 Compare April 22, 2024 02:05
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from b8e0457 to 00ccb51 Compare April 23, 2024 00:01
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 00ccb51 to fa33ad7 Compare April 24, 2024 06:47
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from fa33ad7 to e87b81a Compare April 24, 2024 13:33
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from e87b81a to 2ffcc94 Compare April 25, 2024 01:09
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 2ffcc94 to 661976b Compare April 25, 2024 03:13
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 661976b to 82ff807 Compare April 25, 2024 04:37
@taiko-kitty taiko-kitty changed the title chore(main): release relayer 1.0.0 chore(main): release relayer 0.13.0 May 9, 2024
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch 5 times, most recently from ab1d133 to 2dd418d Compare May 11, 2024 06:27
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 2dd418d to 28c26af Compare May 12, 2024 06:10
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--relayer branch from 28c26af to d44effc Compare May 13, 2024 00:58
@d1onys1us d1onys1us closed this May 13, 2024
@d1onys1us d1onys1us deleted the release-please--branches--main--components--relayer branch May 13, 2024 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants