Skip to content

chore(release): merge dev into main [npm graceful retag fallback]#94

Merged
namastex888 merged 2 commits into
mainfrom
dev
May 26, 2026
Merged

chore(release): merge dev into main [npm graceful retag fallback]#94
namastex888 merged 2 commits into
mainfrom
dev

Conversation

@namastex888
Copy link
Copy Markdown
Collaborator

@namastex888 namastex888 commented May 26, 2026

Merging dev into main to include the graceful npm retag fallback in version.yml.

Summary by CodeRabbit

  • Chores
    • Improved the npm publishing workflow to gracefully handle re-publication scenarios by adding a fallback mechanism that updates package tags instead of failing when a version is already published.

Review Change Stack

automagik-genie and others added 2 commits May 26, 2026 07:52
@namastex888 namastex888 merged commit 02d97a6 into main May 26, 2026
6 of 9 checks passed
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 26, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6f91ad9b-4882-45e3-8653-3135ba1d5e6e

📥 Commits

Reviewing files that changed from the base of the PR and between 5651356 and 02f140e.

⛔ Files ignored due to path filters (2)
  • dist/src/version.d.ts is excluded by !**/dist/**
  • dist/src/version.js is excluded by !**/dist/**
📒 Files selected for processing (1)
  • .github/workflows/version.yml

📝 Walkthrough

Walkthrough

The PR updates .github/workflows/version.yml to improve npm package publishing resilience. The publish step now uses resolved version and tag outputs, attempts publication, and gracefully falls back to applying the npm dist-tag when the version is already published instead of failing.

Changes

npm publishing with fallback

Layer / File(s) Summary
npm publish with dist-tag fallback
.github/workflows/version.yml
The npm publish command now reads resolved VERSION and TAG outputs, publishes with --access public --tag, and on failure falls back to adding or updating the npm dist-tag for @automagik/rlmx at that version instead of erroring out.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • automagik-dev/rlmx#39: Both PRs make npm publish non-fatal when the target version already exists, falling back to applying the intended npm dist-tag instead.
  • automagik-dev/rlmx#32: Both PRs modify npm publish and dist-tag retagging logic for the @automagik/rlmx package within the CI/CD workflow.

Poem

🐰 A rabbit hops with glee,
When publish stumbles gracefully—
No tag survives the retry dance,
The dist-tag gets its second chance! ✨
—a publish workflow, now serene 🚀

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev

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

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the version number from "0.260526.4" to "0.260526.5" in the distribution files version.d.ts and version.js. There are no review comments, and I have no feedback to provide.

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