ci: tweak scripts

[mantricjavier]

Description and Motivation

• Adds the right env values for MANTRA mainnet.
• Tweak ci scripts for getting artifacts versions.

Related Issues

---

Checklist:

• I have read MANTRA's contribution guidelines.
• My pull request has a sound title and description (not something vague like Update index.md)
• All existing and new tests are passing.
• I updated/added relevant documentation.
• The code is formatted properly cargo fmt --all --.
• Clippy doesn't report any issues cargo clippy -- -D warnings.
• I have regenerated the schemas if needed with just schemas.

Summary by CodeRabbit

• New Features
  • Enhanced artifact version retrieval process with improved output formatting.
  • Updated environment variables for blockchain network identification and RPC endpoint.
• Bug Fixes
  • Streamlined output of artifact and package version retrieval to improve readability.

[coderabbitai]

Walkthrough

The changes in this pull request involve modifications to several files to improve the artifact version retrieval process and update environment variables. The workflow file for releasing artifacts has been adjusted to include a --skip-verbose flag in the script execution, affecting output verbosity. The justfile has been updated similarly. Additionally, the mantra.env file has had its blockchain network identifier and RPC endpoint simplified. Lastly, the get_artifacts_versions.sh script has been enhanced with new formatting, conditional output, and improved artifact name handling.

Changes

File Path	Change Summary
.github/workflows/release-artifacts-on-tag.yaml	Updated artifact version retrieval command to include --skip-verbose flag.
justfile	Updated get-artifacts-versions recipe command to include --skip-verbose flag.
scripts/deployment/deploy_env/mainnets/mantra.env	Updated CHAIN_ID from "mantra-hongbai-1" to "mantra-1" and RPC endpoint to a general URL.
scripts/get_artifacts_versions.sh	Enhanced script with conditional verbosity, bold formatting for output, and improved artifact name handling.

Poem

In the burrow where changes bloom,
Scripts and workflows find more room.
With flags that skip the verbose chat,
Our artifacts shine, sleek and flat.
From "mantra-hongbai" to "mantra-1",
A simpler path, oh what fun! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between eb011e6 and 825385e.

📒 Files selected for processing (4)

• .github/workflows/release-artifacts-on-tag.yaml (1 hunks)
• justfile (1 hunks)
• scripts/deployment/deploy_env/mainnets/mantra.env (1 hunks)
• scripts/get_artifacts_versions.sh (1 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.

🪧 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.
  • 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 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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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