Skip to content

Conversation

@allthatjazzleo
Copy link
Contributor

@allthatjazzleo allthatjazzleo commented May 19, 2025

Summary by CodeRabbit

  • Chores
    • Updated the Docker build workflow to use an updated version of the Heighliner build action.

@coderabbitai
Copy link

coderabbitai bot commented May 19, 2025

Walkthrough

The Docker workflow configuration was updated to use a newer version (v1.7.5) of the Heighliner build action by modifying the heighliner-tag input. No other logic, environment variables, or workflow steps were changed.

Changes

File(s) Change Summary
.github/workflows/docker.yml Updated heighliner-tag input from v1.7.3 to v1.7.5 in the build action step.

Poem

A Docker workflow hops ahead,
With Heighliner’s version freshly spread.
From v1.7.3, we leap to .5,
Ensuring our builds continue to thrive.
A simple tag, a subtle cheer—
The rabbit grins, “New builds are here!” 🐇

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch fix/ci-docker-build
  • Post Copyable Unit Tests in Comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@sonarqubecloud
Copy link

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between a14d439 and c715662.

📒 Files selected for processing (1)
  • .github/workflows/docker.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Build - Linux aarch64
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: connect-test (1.23.x, ubuntu-latest-x64-xlarge)
  • GitHub Check: Analyze (go)
  • GitHub Check: Mergify Merge Protections
  • GitHub Check: Summary

# TODO: change back to strangelove-ventures once it create the release
heighliner-owner: ${{ github.repository_owner }}
heighliner-tag: v1.7.3
heighliner-tag: v1.7.5
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Bump Heighliner tag to v1.7.5 – approved.

The Heighliner build action input has been updated from v1.7.3 to v1.7.5 as intended. Please verify that the v1.7.5 release exists in the strangelove-ventures/heighliner-build-action repository and is compatible with your pipelines.
You can run this check without cloning the repo:

Expect a JSON object for refs/tags/v1.7.5; a 404 indicates the tag isn't published yet.


🏁 Script executed:

#!/bin/bash
curl -s https://api.github.com/repos/strangelove-ventures/heighliner-build-action/git/refs/tags/v1.7.5

Length of output: 250


Invalid Heighliner tag – v1.7.5 not found
The GitHub API returned a 404 when checking for refs/tags/v1.7.5 in the strangelove-ventures/heighliner-build-action repo. Please ensure that the v1.7.5 tag has been published or update this workflow to point at an existing release.

• File: .github/workflows/docker.yml
Line 56:

heighliner-tag: v1.7.5
🤖 Prompt for AI Agents
In .github/workflows/docker.yml at line 56, the Heighliner tag is set to v1.7.5,
but this tag does not exist in the strangelove-ventures/heighliner-build-action
repository, causing a 404 error. To fix this, verify the available tags in the
repository and update the heighliner-tag value to a valid, existing tag that is
compatible with your pipeline.

@allthatjazzleo allthatjazzleo merged commit b63b1c4 into main May 19, 2025
24 checks passed
@freeelancer freeelancer deleted the fix/ci-docker-build branch May 19, 2025 16:31
freeelancer added a commit that referenced this pull request May 21, 2025
* wip: upgraded cosmos/evm to v0.2.0

* update ibc to v10

* add clienthelpers for defaultNodeHome

* fix: update heighliner tag to v1.7.5 (#325)

* update swagger api with latest versions

---------

Co-authored-by: Leo Pang <[email protected]>
freeelancer added a commit that referenced this pull request Jun 18, 2025
* remove skip-mev feemarket

* wired in evm, erc20 from evmos

* added back bank send hook

* updated swagger to include evmos modules

* replace default denom from uom to aom with 18dp

* genesis file for omstead testnet

* register swagger statik with namespace (temporary)

* add ante import to app

* Revert "register swagger statik with namespace (temporary)"

This reverts commit 20b1bde.

* add swagger.go

* switch from evmos evm to cosmos evm

* fix compile error

* add secp256k1 keys for sigverify

* feat: pump go in release.yml

* fix: GORELEASER_IMAGE is outdated

* fix: rest apis and evm routes

* feat: remove validation for CosmosChainID and fix base to 6 decimals

* feat: update dependencies + add client context

* fix: remove duplicate keyring options

* fix: update to use cosmos evm tracers

* refactor: consolidate setup configuration for address prefixes and cointype (#315)

* refactor: consolidate setup configuration for address prefixes and cointype

* fix: lint

---------

Co-authored-by: freeelancer <[email protected]>

* Merge branch 'main' into main-evm (#320)

* chore: remove networks folder

* feat: cosmos/evm v0.2.0 + ibc v10 (#326)

* wip: upgraded cosmos/evm to v0.2.0

* update ibc to v10

* add clienthelpers for defaultNodeHome

* fix: update heighliner tag to v1.7.5 (#325)

* update swagger api with latest versions

---------

Co-authored-by: Leo Pang <[email protected]>

* feat: upgrade from v4 to v5-evm with migration

* chore: remove xfeemarket module

* chore(deps): update github.com/cosmos/evm to v1.0.0-rc0

* feat: burn transaction fees

* chore(deps): update cosmos-sdk fork from v0.53.0-v5-mantra-1 to v0.53.0-v5-mantra-1-1

* chore(deps): update github.com/cosmos/evm with latest main branch commit

* chore: comment out linux/arm64 platform in chains.yaml

* fix(test): e2e tests (#330)

* feat: move burn fees from antehandler to tax endblocker (#332)

* update go.mod for connect

* revert to using default cosmos evm antehandler

* remove xfeemarket leftover

* feat: burn fees using tax endblocker

* feat: init evm chain id from genesis.json or app.toml (#338)

* feat: init evm chain id from genesis.json or app.toml

* remove constant.go and move code over to config.go

* avoid unexpected err

* avoid oom for big genesis

* cleanup

---------

Co-authored-by: mmsqe <[email protected]>

* chore: remove IBC v2 and precompile support temporarily (#340)

* feat: allow only single evm msg (#341)

* feat: remove legacy feemarket (skip-mev) store entirely (#342)

* chore: remove past upgradehandlers

* fix: remove legacy feemarket store entirely

* feat: add nix e2e test

* fix: evm init params (#344)

* fix: evm initial params

* chore: add v5.0.0-rcx to mergify

* chore: remove main-evm from condition

---------

Co-authored-by: allthatjazzleo <[email protected]>

* chore: remove networks folder (#346)

---------

Co-authored-by: allthatjazzleo <[email protected]>
Co-authored-by: Leo Pang <[email protected]>
Co-authored-by: mmsqe <[email protected]>
mergify bot pushed a commit that referenced this pull request Sep 8, 2025
(cherry picked from commit b63b1c4)

# Conflicts:
#	.github/workflows/docker.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants