# Maintaining dsh-jj-vcs

## Supported baseline

The current maintained baseline is Jujutsu 0.44.0. The installed command help is authoritative when it differs from repository prose.

## Upgrade verification

Install the candidate Jujutsu version in an isolated environment. Read the official release notes and the installed top-level and command-specific help. Then run:

```sh
node skills/dsh-jj-vcs/scripts/verify-jj-compat.mjs --upgrade --skip-repo
node skills/dsh-jj-vcs/scripts/verify-jj-task.mjs
```

Review changes to workspace creation, templates, operation handling, conflict diagnostics, Git import and export, bookmark and tag tracking, fetch and push selectors, bypass flags, and Windows symlink behavior.

After the candidate behavior is understood, update `skills/dsh-jj-vcs/compatibility.json`, the audited version in `SKILL.md`, `references/version-and-upgrades.md`, this file, and `.github/workflows/verify.yml`. Run the verifier again without `--upgrade`; exact-version mode must pass before release.

## Package release

Keep `package.json` and `.codex-plugin/plugin.json` on the same semantic version. Run package, provider, plugin, skill, and JJ verification. Inspect `npm pack --dry-run --json` to confirm that the skill references and scripts are included.

Create or move one release bookmark at the reviewed change. Fetch the intended remote and run an exact-bookmark dry run before an authorized push. Tagging and GitHub release publication remain separate remote-visible actions.