Skip to content

ci: Update LATEST version to 9.6.1 in release workflow#141

Merged
cbaker6 merged 1 commit intomainfrom
cbaker6-patch-1
Mar 24, 2026
Merged

ci: Update LATEST version to 9.6.1 in release workflow#141
cbaker6 merged 1 commit intomainfrom
cbaker6-patch-1

Conversation

@cbaker6
Copy link
Copy Markdown
Member

@cbaker6 cbaker6 commented Mar 24, 2026

No description provided.

Copilot AI review requested due to automatic review settings March 24, 2026 08:26
@cbaker6 cbaker6 merged commit 2f272b0 into main Mar 24, 2026
4 of 5 checks passed
@cbaker6 cbaker6 deleted the cbaker6-patch-1 branch March 24, 2026 08:26
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 24, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e15c3425-985f-4db5-bd66-6589b8f2713a

📥 Commits

Reviewing files that changed from the base of the PR and between a4ce40e and 229b589.

📒 Files selected for processing (1)
  • .github/workflows/release.yml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the designated latest release version to 9.6.1, affecting Docker image distribution and tagging.

Walkthrough

HAHAHAHA! A MOST EXCELLENT UPDATE, I SAY! The workflow environment variable LATEST has been upgraded from version '9.5.1' to '9.6.1', changing which Docker image tags receive the "latest" designation and associated metadata labels during release!

Changes

Cohort / File(s) Summary
Release Workflow Configuration
.github/workflows/release.yml
Updated LATEST environment variable from '9.5.1' to '9.6.1', affecting Docker metadata labels and conditional build/push logic for latest release tagging.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • PR #126: Updates the same .github/workflows/release.yml file's LATEST variable to designate a new release version
  • PR #127: Modifies LATEST environment variable in the release workflow to update which tag receives "latest" designation
  • PR #128: Changes the LATEST version in the release workflow, affecting conditional build and push steps for latest releases

Poem

✨ From five-point-one, we rise so high! ✨

A version climbs, from old to new,

9.6.1 shines through and through!

The latest tag does point the way,

PLUS ULTRA—a glorious release day! 💪

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cbaker6-patch-1

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the release workflow’s notion of the “latest” tagged release so that only tag 9.6.1 is treated as latest for Docker/Singularity publishing.

Changes:

  • Bumped the LATEST environment variable from 9.5.1 to 9.6.1 in the GitHub Actions release workflow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants