Prepare release 2.2.0: changelog section and guides at @v2 #216

Merged
Tirsvad merged 1 commits from release-2.2.0 into main 2026-10-21 13:40:34 +02:00
Owner

Prepares release 2.2.0 of this repository: the changelog section and the guides, so that the tag holds correct documentation.

What this changes

  • CHANGELOG.md: the unreleased entries become ## [2.2.0] - 2026-10-21 (the english-comments.yml workflow, actions/connect-wireguard, actions/connect-tailscale). A minor release (ADR-0006); MAJOR_TAG stays v2.
  • The guides of the English-comments workflow and of the two VPN actions call @v2 instead of @main, and the notes "until release ... call @main" are removed. The English-comments wiki page and its Danish and Bahasa Malaysia translations follow (hashes updated).
  • The VPN guides say the actions are released in 2.2.0 and have not yet run on a runner with a real tunnel.

What the release means

v2 will move to 2.2.0, so every caller at @v2 receives the new workflow and actions. The VPN actions have not run with a real WireGuard peer or tailnet (MIL-012 tasks 2 to 5 are open), and the check is not required in any repository yet (MIL-013 task 9). Both are stated in the guides. The tag, the release page and the moving tag are made by the Release workflow after this merges (a dry run first).

Issues

No issue closed: the tasks they describe are partly open.

Refs #188
Refs #191
Refs #207

Prepares release 2.2.0 of this repository: the changelog section and the guides, so that the tag holds correct documentation. ## What this changes - `CHANGELOG.md`: the unreleased entries become `## [2.2.0] - 2026-10-21` (the `english-comments.yml` workflow, `actions/connect-wireguard`, `actions/connect-tailscale`). A minor release ([ADR-0006]); `MAJOR_TAG` stays `v2`. - The guides of the English-comments workflow and of the two VPN actions call `@v2` instead of `@main`, and the notes "until release ... call `@main`" are removed. The English-comments wiki page and its Danish and Bahasa Malaysia translations follow (hashes updated). - The VPN guides say the actions are released in 2.2.0 and have **not yet run on a runner with a real tunnel**. ## What the release means `v2` will move to 2.2.0, so every caller at `@v2` receives the new workflow and actions. The VPN actions have not run with a real WireGuard peer or tailnet (MIL-012 tasks 2 to 5 are open), and the check is not required in any repository yet (MIL-013 task 9). Both are stated in the guides. The tag, the release page and the moving tag are made by the Release workflow after this merges (a dry run first). ## Issues No issue closed: the tasks they describe are partly open. Refs #188 Refs #191 Refs #207 [ADR-0006]: docs/adr/adr-0006-release-process-and-version-pinning.md
Tirsvad added 1 commit 2026-10-21 13:39:28 +02:00
Prepare release 2.2.0: changelog section and guides at @v2
TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Skipped
Validate workflows / validate (pull_request) Successful in 58s
01178370cb
The unreleased entries become the 2.2.0 section (the English-comments workflow
and the WireGuard and Tailscale actions). The guides no longer say to call
@main until a release: the examples use @v2, and the VPN guides state that the
actions are released but have not run on a real tunnel yet.

Refs #188
Refs #191
Refs #207
Tirsvad merged commit e33b9977a3 into main 2026-10-21 13:40:34 +02:00
Tirsvad deleted branch release-2.2.0 2026-10-21 13:40:34 +02:00
Sign in to join this conversation.