ci: Added goreleaser check

[CharlieMc0]

Description

Added a dry run of goreleaser as part of the release workflow. Not having a test of goreleaser caused issued with the v19 release because it had not been properly updated. https://github.com/zeta-chain/node/actions/runs/10252637202

How Has This Been Tested?

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

Summary by CodeRabbit

• New Features

  • Introduced a new job in the release workflow that performs a dry run of the release process, enhancing the reliability of future releases.

• Improvements

  • Standardized naming conventions for workflow jobs to improve clarity and consistency throughout the release process.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Walkthrough

The recent changes enhance the GitHub Actions workflow in publish-release.yml by renaming the check_branch job to check-branch for consistency and clarity. Additionally, a new job named check-goreleaser has been introduced, which executes a make release-dry-run command to improve the release process. This structural update fosters better organization of the workflow while expanding its functionality.

Changes

Files	Change Summary
.github/workflows/publish-release.yml	Renamed job check_branch to check-branch. Added new job check-goreleaser for release dry run.

Sequence Diagram(s)

sequenceDiagram
    participant A as check-branch
    participant B as check-changelog
    participant C as check-upgrade-handler-updated
    participant D as check-goreleaser
    participant E as final-job

    A->>B: Checks changelog
    A->>C: Checks upgrade handler
    A->>D: Executes make release-dry-run
    B->>E: Completes and triggers final job
    C->>E: Completes and triggers final job
    D->>E: Completes and triggers final job

Loading

---

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.
  • @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 as 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.

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

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3b0431e and c284bb0.

Files selected for processing (1)

• .github/workflows/publish-release.yml (3 hunks)

Additional comments not posted (5)

.github/workflows/publish-release.yml (5)

26-26: Approved: Renaming for consistency.

The job check_branch has been renamed to check-branch for consistency. Ensure that all references to this job are updated accordingly.

---

34-41: Approved: Addition of check-goreleaser job.

The new job check-goreleaser runs a make release-dry-run command to enhance the release process by identifying potential issues before an actual release. This addition is well-justified and improves reliability.

---

45-45: Approved: Dependency update for check-changelog.

The job check-changelog now correctly depends on check-branch, ensuring logical sequencing in the workflow.

---

87-87: Approved: Dependency update for check-upgrade-handler-updated.

The job check-upgrade-handler-updated now correctly depends on check-branch, ensuring logical sequencing in the workflow.

---

126-126: Approved: Dependency update for publish-release.

The job publish-release now correctly depends on check-branch, ensuring logical sequencing in the workflow.