cleanup: retire stale version bump wrappers #389

Closed
opened 2026-05-12 13:17:40 +00:00 by barrettruth · 0 comments
Owner

Problem

The top-level just release <surface> <target> command is now the intended release path, but old wrapper scripts still exist (scripts/bump-version.sh, scripts/version/bump-app.sh, scripts/version/bump-cli.sh, scripts/version/next-version.sh). They create multiple entrypoints with different levels of validation and make release behavior harder to reason about.

Solution

  • Remove stale wrapper scripts or reduce them to one clearly documented compatibility entrypoint if a package script still needs it.
  • Keep scripts/version/bump.sh and scripts/version/cli.mjs as the authoritative implementation.
  • Ensure package scripts and docs point to just release <surface> <target> / pnpm release consistently.
  • Keep version and generated manpage checks green.

Non-goals

  • Do not change release semantics or tagging policy.
  • Do not expand the justfile with extra release commands.
  • Do not remove npm token preflight checks.

Part of #184 and #355.

## Problem The top-level `just release <surface> <target>` command is now the intended release path, but old wrapper scripts still exist (`scripts/bump-version.sh`, `scripts/version/bump-app.sh`, `scripts/version/bump-cli.sh`, `scripts/version/next-version.sh`). They create multiple entrypoints with different levels of validation and make release behavior harder to reason about. ## Solution - Remove stale wrapper scripts or reduce them to one clearly documented compatibility entrypoint if a package script still needs it. - Keep `scripts/version/bump.sh` and `scripts/version/cli.mjs` as the authoritative implementation. - Ensure package scripts and docs point to `just release <surface> <target>` / `pnpm release` consistently. - Keep version and generated manpage checks green. ## Non-goals - Do not change release semantics or tagging policy. - Do not expand the justfile with extra release commands. - Do not remove npm token preflight checks. Part of #184 and #355.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/delta#389
No description provided.