fix(ci): remove pnpm version input conflicting with packageManager

[evilpeach]

Summary

• pnpm/action-setup@v4 fails with "Multiple versions of pnpm specified" when the workflow passes version: while package.json declares a packageManager field — this broke the build-and-publish job on the v0.13.1 tag push (https://github.com/initia-labs/tx-decoder/actions/runs/27392863202/job/80953995812), so 0.13.1 was never published to npm.
• The conflict became live when fix(schema): accept proto-JSON Any in tx body extension_options #113 re-added "packageManager": "pnpm@11.0.8"; this removes the version: latest input so the publish workflow uses the pinned version from packageManager, matching ci-tests.yml (which already omits the input and passes on the same commit).
• Note: re-running the failed v0.13.1 run will NOT pick up this fix (re-runs use the workflow at the tag's SHA). After merging, either re-point the v0.13.1 tag to the fixed commit or publish 0.13.1 manually.

Summary by CodeRabbit

• Chores
  • Updated internal build workflow configuration.

---

No user-facing changes in this release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1490ed05-c4c0-4ac4-899e-561a95b45f53

📥 Commits

Reviewing files that changed from the base of the PR and between c3c6b9a and 640eb0f.

📒 Files selected for processing (1)

• .github/workflows/release-and-publish.yml

💤 Files with no reviewable changes (1)

• .github/workflows/release-and-publish.yml

---

Walkthrough

The release-and-publish workflow's pnpm action setup step has been simplified by removing its explicit version: latest configuration. The action now uses its default version behavior while all subsequent build and publish steps remain unchanged.

Changes

Release Workflow Configuration

Layer / File(s)	Summary
Pnpm action configuration simplification .github/workflows/release-and-publish.yml	The pnpm/action-setup@v4 step's explicit version: latest configuration block was removed, allowing the action to use its default version resolution instead of pinning to the latest available version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A tiny tweak, a config cleaned,
Remove the version, let defaults gleam!
The workflow now flows more naturally free,
With less constraint, the pnpm way to be. ✨

🚥 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 title clearly and specifically describes the main change: removing the pnpm version input from CI configuration due to a conflict with packageManager field.
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 peach/fix-pnpm-setup-conflict

---

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