[goreleaser] Submitter: adjust Gas Tip Minimum Comparison

[aureliusbtc]

Description
A clear and concise description of the features you're adding in this pull request.

Additional context
Add any other context about the problem you're solving.

Metadata

• Fixes #[Link to Issue]

Summary by CodeRabbit

• Refactor
  • Updated the logic for setting GasTipCap to enhance transaction efficiency under specific conditions.

[coderabbitai]

Walkthrough

The recent update involves a crucial adjustment in the submitter.go file, where the logic for determining GasTipCap has been refined. Instead of comparing with gasFloor, it now judiciously compares with minTipCap, enhancing the efficiency and accuracy of gas fee calculations.

Changes

File Path	Change Summary
.../submitter/submitter.go	Updated GasTipCap logic to compare with minTipCap instead of gasFloor.

🐇✨
In the code where bytes dance and play,
A small change makes a big wave today.
No longer a floor, but a minimum cap,
Ensures our transactions never mishap.
So here's to the code, refined and bright,
May your gas fees be ever so light.
🚀🌌

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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 testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.12097%. Comparing base (2e866d6) to head (608da60).

Additional details and impacted files

@@                 Coverage Diff                 @@
##              master       #2468         +/-   ##
===================================================
- Coverage   47.15101%   47.12097%   -0.03004%     
===================================================
  Files            382         399         +17     
  Lines          29098       30479       +1381     
  Branches          83          83                 
===================================================
+ Hits           13720       14362        +642     
- Misses         13936       14602        +666     
- Partials        1442        1515         +73     

Flag	Coverage Δ
cctp-relayer	43.53414% <ø> (?)
committee	62.20028% <ø> (ø)
omnirpc	53.23194% <ø> (ø)
promexporter	75.91241% <ø> (?)
rfq	28.93849% <ø> (ø)
scribe	52.02703% <ø> (-0.18427%)	⬇️
sin-executor	61.57635% <ø> (ø)
stiprelayer	3.33333% <ø> (ø)
tools	21.98661% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 2e866d6 and 608da60.

Files selected for processing (1)

• ethergo/submitter/submitter.go (1 hunks)

Additional comments not posted (1)

ethergo/submitter/submitter.go (1)

449-449: Adjust the comparison logic for GasTipCap to use minTipCap.

This change aligns with the PR's objective to adjust the comparison logic for GasTipCap from comparing against gasFloor to comparing against minTipCap. It's a targeted improvement aimed at optimizing gas price handling for transactions.

[cloudflare-workers-and-pages]

Deploying sanguine-fe with    Cloudflare Pages

Latest commit:	608da60
Status:	✅  Deploy successful!
Preview URL:	https://b3dcab3a.sanguine-fe.pages.dev
Branch Preview URL:	https://submitter-gas-floor-tip-comp.sanguine-fe.pages.dev

View logs