Align release and publish automation

[alexbit-codemod]

Summary

• run CI on main and test only affected codemods in pull requests
• separate release PR creation from codemod tagging and publishing
• replace the platform-specific YAML version sync script with a Node implementation

Test plan

• pnpm run ci
• exercise sync-codemod-yaml-versions.mjs without metadata churn
• run tag-and-publish.mjs with DRY_RUN=1
• run syntax, lint, and diff checks

Made with Cursor

[Copilot]

Pull request overview

Aligns the repository’s release/publish automation by splitting “create release PR” from “tag + publish”, tightening CI triggering behavior, and replacing the bash-based version sync step with a Node script.

Changes:

• Update CI to run on main and (for PRs) run tests only for changed codemod packages.
• Split release automation into separate Release (release PR creation) and Publish (tagging + publishing) workflows.
• Replace the bash codemod.yaml version sync script with a Node implementation and introduce .nvmrc for Node version pinning.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
scripts/sync-codemod-yaml-versions.mjs	New Node script to sync codemod.yaml versions from each codemod’s package.json.
scripts/sync-codemod-versions.sh	Removed prior bash/sed-based YAML version sync implementation.
package.json	Switch version-packages to use the new Node sync script.
.nvmrc	Pins Node version for workflows/tools that use node-version-file.
.github/workflows/release.yml	Now only creates the release PR (publishing removed).
.github/workflows/publish.yml	New workflow to tag released versions and publish affected codemods.
.github/workflows/ci.yml	Restrict CI to main and add “test only changed codemods” logic for PRs.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.