Skip to content

v2026.6.6

Choose a tag to compare

View all tags
@jmagly jmagly released this 21 Jun 22:00
· 787 commits to main since this release
v2026.6.6
f6fcd61
This commit was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 0117DAAA677A5BF2
Verified
Learn about vigilant mode.

AIWG 2026.6.6 — "Release-pipeline hardening, cont."

Released: 2026-06-21
Channel: stable (npm install -g aiwg)

Follow-on hardening surfaced while validating 2026.6.5's GitHub-mirror fix. No
CLI or API changes.

Fixes

GitHub mirror tag-push is idempotent

After 2026.6.5 corrected the mirror's secret name, the mirror job started
actually running — and exposed that its tag-push to the GitHub mirror was not
idempotent: if the tag already existed (a re-run, or a manual push that raced
the workflow), git push failed with "tag already exists" and the job aborted
before creating the GitHub Release.

github-mirror.yml now tolerates an already-present tag (the same || echo
guard the main-push already had) and proceeds to Release creation. The Release
step itself was already idempotent (it checks for an existing release first).

Docsite strict-link build

The v2026.6.4 and v2026.6.5 announcements linked the CHANGELOG with a relative
../../CHANGELOG.md path that resolves outside the published docs tree, which
failed the docsite's strict-link check. They now use the absolute GitHub URL,
matching every prior announcement.

Release runbook

CLAUDE.md / AIWG.md step 8 no longer instructs a manual git push github.
The Gitea tag push (step 7) triggers github-mirror.yml, which pushes main +
the tag to the GitHub mirror and creates the GitHub Release itself. The
manual push raced the workflow's own tag push; the runbook now says not to do
it.

Upgrade

npm install -g aiwg     # 2026.6.6
aiwg version            # → 2026.6.6 [stable]

No action required. Tooling/release-process release.

Links

Assets 2
Loading