fix(ci): allow same-version npm bump in wasm publish workflows

[goldmedal]

Summary

The release-please-driven stable publish failed at the Set version in package.json step:

```

• npm version "0.2.0" --no-git-tag-version
  VERSION: 0.2.0
  npm error Version not changed
  ```

release-please-action bumps package.json as part of the release PR. Once that PR merges into main, the package.json version on main already matches the released tag, so npm version 0.2.0 errors out with "Version not changed".

Fix

Pass --allow-same-version so the bump is a no-op when the version already matches. Apply to both wasm publish workflows:

• publish-wren-core-wasm.yml (OIDC, release-please) — directly fixes the failing path.
• publish-wren-core-wasm-rc.yml (token, RC) — RC won't normally hit this since -rc.N versions always differ from main, but mirrors the change to keep the two pipelines in sync.

Test plan

• Re-run the Release Please workflow (or the next merge that bumps wasm). Confirm Set version in package.json succeeds and npm publish follows.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Improved release automation to avoid failures when a package version is already set, making RC and stable releases more robust.
  • Updated the release manifest entry for the wasm package to adjust the recorded version mapping.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0640da36-5b78-4903-96a9-4c126d54a038

📥 Commits

Reviewing files that changed from the base of the PR and between 4350739 and cde136f.

📒 Files selected for processing (1)

• .release-please-manifest.json

---

Walkthrough

Workflows that set package.json version for wren-core-wasm now pass --allow-same-version to npm version to avoid failing when the file already matches the requested version. The release-please manifest mapping for core/wren-core-wasm was changed from 0.2.0 to 0.1.0.

Changes

Publish Workflow Changes

Layer / File(s)	Summary
Control step update .github/workflows/publish-wren-core-wasm.yml, .github/workflows/publish-wren-core-wasm-rc.yml	npm version "$VERSION" invocations now include --allow-same-version (and keep --no-git-tag-version in RC), with inline comments explaining release-please or OIDC behavior.

Release-Please Manifest Update

Layer / File(s)	Summary
Manifest mapping .release-please-manifest.json	core/wren-core-wasm version mapping changed from 0.2.0 → 0.1.0 (other entries unchanged).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Canner/WrenAI#2240: Modifies the same RC publish workflow’s npm version step.
• Canner/WrenAI#2232: Edits the publish-wren-core-wasm workflow and related publish/auth logic.
• Canner/WrenAI#2231: Changes release-please manifest handling and per-package version behavior.

Suggested labels

wasm

Suggested reviewers

• PaulChen79
• grieve54706

Poem

🐰 A tiny hop on release night’s lawn,
I add a flag so errors are gone,
If release-please already set the tune,
The publish step hums and finishes soon,
A cheerful thump, and the pipelines move on.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and specifically describes the main change: adding --allow-same-version to npm version commands in WASM publish workflows to handle cases where release-please has already bumped the version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/wasm-publish-allow-same-version

---

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