fix: idempotent release workflow

[namastex888]

Skip release creation when tag already exists + retag as latest when version already published from @next.

Merge with "Create a merge commit" — NEVER squash.

Summary by CodeRabbit

• Chores

  • Version bumped to 3.260316.15 across plugin manifests and package configurations.

• Bug Fixes

  • Release workflow now checks for existing releases before creation, preventing duplicate GitHub releases from being generated when rerunning the pipeline.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the robustness and reliability of the release workflow by implementing idempotency. The changes ensure that the release process is more resilient against duplicate releases and correctly manages 'latest' tags, particularly for versions originating from development branches.

Highlights

• Release Idempotency: The release workflow has been updated to skip the creation of a new release if the corresponding tag already exists, preventing redundant releases.
• Latest Tag Management: The workflow now includes logic to correctly retag a version as 'latest' if it was previously published from a '@next' branch, ensuring accurate version progression.

Changelog

• .claude-plugin/marketplace.json
  • Updated the 'version' field from "3.260316.14" to "3.260316.15".
• openclaw.plugin.json
  • Updated the 'version' field from "3.260316.14" to "3.260316.15".
• package.json
  • Updated the 'version' field from "3.260316.14" to "3.260316.15".
• plugins/genie/.claude-plugin/plugin.json
  • Updated the 'version' field from "3.260316.14" to "3.260316.15".
• plugins/genie/package.json
  • Updated the 'version' field from "3.260316.14" to "3.260316.15".

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release.yml

Activity

• No specific activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the version number across several configuration files, likely as part of an automated release process. While the changes are straightforward, the new version number (3.260316.15) appears to be based on a future date (March 16, 2026), according to the project's versioning script. This is an unconventional practice that can lead to confusion and potential issues with version management. I have added a comment on package.json to highlight this concern.

[gemini-code-assist]

The versioning scheme appears to be based on a future date. The new version 3.260316.15 suggests a date of March 16, 2026, based on the 3.YYMMDD.N format described in scripts/version.ts. Using future dates for versioning is unconventional, can be confusing, and may cause issues with version sorting and dependency management tools. It is recommended to revise the version generation logic in scripts/version.ts to use the current date.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 18f03c57-b2c4-4eda-a49e-525a0989cccd

📥 Commits

Reviewing files that changed from the base of the PR and between 65673fc and 40ae7b9.

📒 Files selected for processing (6)

• .claude-plugin/marketplace.json
• .github/workflows/release.yml
• openclaw.plugin.json
• package.json
• plugins/genie/.claude-plugin/plugin.json
• plugins/genie/package.json

---

📝 Walkthrough

Walkthrough

Version number incremented from 3.260316.14 to 3.260316.15 across six configuration files. GitHub release workflow updated to conditionally create releases only if the release tag does not already exist.

Changes

Cohort / File(s)	Summary
Version Bumps .claude-plugin/marketplace.json, openclaw.plugin.json, package.json, plugins/genie/.claude-plugin/plugin.json, plugins/genie/package.json	Version incremented from 3.260316.14 to 3.260316.15 across plugin and package metadata files.
Release Workflow .github/workflows/release.yml	Added conditional check to verify release tag existence via gh release view before creating the release; skips creation if tag already exists.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• PR #515: Modifies the same release workflow file with different release creation logic (auth, first-release handling, notes-file behavior).
• PR #517: Also modifies .github/workflows/release.yml with workflow changes to the publish step (disables husky).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

📝 Coding Plan

• Generate coding plan for human review comments

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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