prepare-package-release

Prepare Package Release

Keep the release version synchronized, update the repository wiki from the complete release diff, and leave tag and artifact creation to the publish workflow.

Follow the workflow

1. Inspect git status, the branch diff against origin/main, package.json, the plugin manifests, and the current release guidance:

   git fetch origin main --tags
   git diff --stat origin/main...HEAD
   codealmanac show guides/release/prepare-package-release
   

2. Confirm the intended semantic version. Treat package.json as the release version source of truth. Ask the user if the task does not establish the bump level.

3. Run npm's version command without creating a commit or tag:

   npm version <patch|minor|major|version> --no-git-tag-version
   

   Synchronize that exact version in:

   • package-lock.json at the root version and packages[""].version;
   • .codex-plugin/plugin.json;
   • .claude-plugin/plugin.json;
   • .claude-plugin/marketplace.json at both the plugin version and npm source version.

   Do not create or push a release tag. The publish workflow creates the tag and GitHub Release after merge.

4. Find the previous release tag after the manifests are synchronized:

   previous_release_tag="$(
     git describe --tags --match 'rudder-plugin-v*' --abbrev=0
   )"
   release_range="${previous_release_tag}..HEAD"
   

   Stop and ask the user if no previous release tag exists. Do not use origin/main as the source boundary. Merged changes since the previous tag still belong to the release.

5. Run CodeAlmanac Ingest for every version bump. Give it the complete committed release range plus staged and unstaged edits:

   guidance="Update durable release knowledge and version claims."
   guidance+=" A no-op is valid."
   codealmanac ingest "git:range:${release_range}" git:diff \
     --title "Document Rudder release <version>" \
     --guidance "$guidance"