Bump package version to 0.2.2 and publish from publish.yml

[eiei114]

Summary

• bump package version from 0.2.0 to 0.2.2
• move npm publish back to .github/workflows/publish.yml to match the current trusted publisher setup
• keep .github/workflows/auto-release.yml focused on tag/release creation
• carry over safer publish workflow behavior for checkout pinning and npm 404 handling

Validation

• npm run check

Context

Sibling OSS repos use the split pattern too:

• auto-release.yml creates the tag/release
• publish.yml handles npm publishing via trusted publishing

Summary by CodeRabbit

• Chores
  • Package version bumped to 0.2.2
  • Updated CI/CD workflows for release and publishing processes

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e78ee204-5ec5-4dba-9643-59ffcd9f16f2

📥 Commits

Reviewing files that changed from the base of the PR and between 0ab60c7 and 583f68a.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• .github/workflows/auto-release.yml
• .github/workflows/publish.yml
• README.md
• package.json

💤 Files with no reviewable changes (1)

• .github/workflows/auto-release.yml

---

📝 Walkthrough

Walkthrough

This PR restructures the release workflow by removing npm publishing from the auto-release job, hardening the standalone publish workflow with action SHAs and improved error handling, and coordinating a version bump from 0.2.1 to 0.2.2 across package.json and README.

Changes

Release Workflow Restructuring and Version Coordination

Layer / File(s)	Summary
Auto-release workflow simplification .github/workflows/auto-release.yml	The release job's exported outputs (released, tag) are removed and the entire downstream publish job is deleted, leaving auto-release to only create git tags and GitHub releases.
Publish workflow hardening .github/workflows/publish.yml	Action versions are pinned to specific commit SHAs instead of floating v4 tags, and the "Skip already published version" step refactored to capture npm view output and explicitly handle E404/404 as "publishable" while failing on other errors.
Version coordination package.json, README.md	Package version is updated from 0.2.1 to 0.2.2 in both package.json and the README's install snippet.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• eiei114/pi-weighted-model-router#2: This PR reverses the addition of jobs.release outputs and the jobs.publish job that were introduced there, restructuring release responsibilities.
• eiei114/pi-weighted-model-router#3: Both PRs coordinate package version changes, with this PR's 0.2.1→0.2.2 bump building on the version management patterns established in the related PR.

Poem

🐰 We hop away from auto-release's load,
Publish now walks its own steady road.
Actions pinned tight, errors handled with care,
Version bumped up: 0.2.2 in the air! 🚀

🚥 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 accurately summarizes the two main changes: bumping the package version to 0.2.2 and moving npm publishing to publish.yml workflow.
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 bump-version-0-2-2

---

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

[coderabbitai]

Actionable comments posted: 0