Skip to content

docs: release v2.0.0 — the plugin is adf, and AGENTS.md is the one instruction file - #62

Merged
mauricios merged 1 commit into
mainfrom
docs/release-v2.0.0
Oct 9, 2026
Merged

mauricios merged 1 commit into
mainfrom
docs/release-v2.0.0

Conversation

@mauricios

Copy link
Copy Markdown
Contributor

The v2.0.0 release PR, following CONTRIBUTING.md § Cutting a release. It's a major release under decision 0017: every project has to act once, because the plugin is renamed and CLAUDE.md goes away.

Changes

  • CHANGELOG.md: Unreleased becomes ## v2.0.0 — 2026-10-09 — The plugin is adf, and AGENTS.md is the one instruction file, with an empty Unreleased above it. The section opens with:
    • what the release brings: plugins by concern (0023); AGENTS.md as the one instruction file (0024, 0025); the local environment's conventions (0032); the plugins as the machinery's source (0027–0030); agent model overrides (0031);
    • the order to upgrade from v1.x, which replaces the short "Upgrading from v1" note:
      1. update Claude Code to v2.1.281 or later;
      2. run /aplyca-adf:upgrade. In one draft PR it does the rename, CLAUDE.md, GEMINI.md, the move to ops/agent/, the committed machinery, and the project's layer;
      3. each developer reinstalls the plugin under its new name and removes a stray CLAUDE.md / CLAUDE.local.md;
      4. optionally turn on adf-dev and adf-connect.
  • Version: plugins/adf/.claude-plugin/plugin.json is 2.0.0, and scripts/build-plugins.sh carried it into adf-dev and adf-connect.
  • plugins/adf/README.md: the settings example pins v2.0.0.
  • README.md:

Before merging

  • Rehearse the v1.4.0 → v2.0.0 upgrade on a real project, committed and packaged. The newest dynamic eval reports are from 2026-10-05, before 0024, 0027, 0028, and 0032 landed. An earlier session had a rehearsal-v2/fw-v1.4.0 worktree, so a rehearsal may already be in progress.
  • Merge test: the plugin suites on Haiku 5.5 #51 first if it should ship in v2.0.0. It's test-only, so it needs no changelog entry.
  • Re-check the date in the heading if the merge isn't on 2026-10-09.

After merging

Tag the merge commit v2.0.0 and push the tag. Packaged projects pin it, and without it they can't take the release.

Checks

  • python3 scripts/build-committed.py --check: 57 files round-trip unchanged.
  • ./evals/run-evals.sh: all static suites pass (178, 93, 69, and 39 checks), including the one that holds every plugin's version equal to the newest release in the changelog.

🤖 Generated with Claude Code

…struction file

A major release: every project acts once. The changelog's Unreleased
section becomes v2.0.0, opened with what the release brings and the
order to upgrade from v1.x in: update Claude Code, run
/aplyca-adf:upgrade (the rename, CLAUDE.md and GEMINI.md, the
parallel-agents move to ops/agent/, the committed machinery, the
project's layer), then each developer reinstalls the plugin under its
new name.

- adf's version is 2.0.0; build-plugins.sh carries it into adf-dev
  and adf-connect.
- plugins/adf/README.md pins v2.0.0 in its settings example.
- README.md names v2.0.0 as the latest, says /aplyca-adf:upgrade for
  a project still on v1, and says again that v1.0.0 renamed the plugin
  aplyca-adf; the v2 rename had changed that line to adf.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mauricios
mauricios marked this pull request as ready for review October 9, 2026 19:22
@mauricios
mauricios merged commit 4e62d44 into main Oct 9, 2026
1 check failed
@mauricios
mauricios deleted the docs/release-v2.0.0 branch October 9, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant