From 5ea6e3a4f208c20edca56d9635bfb9aa2f4b3f32 Mon Sep 17 00:00:00 2001 From: Komol Nath Roy Date: Sun, 1 Nov 2026 19:05:26 -0500 Subject: [PATCH] release: v2.2.0 --- CHANGELOG.md | 2 +- RELEASE.md | 1 + internal/version/version.go | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1b2d03b9..7af4283d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,7 @@ Notable changes, newest first. Versions follow [semantic versioning](https://semver.org): from 1.0.0 the exported API is stable, and a breaking change means 2.0 with a new module path. See *Stability* below. -## Unreleased +## v2.2.0 — 2026-11-01 Memory footprint work: what a tree holds and what a transform peaks at. Output is byte-identical; new API is additive. diff --git a/RELEASE.md b/RELEASE.md index 03ced756..98717fe4 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -228,6 +228,7 @@ one**, and the workflow does not try to derive it: | v2.0.3 | w3cschemas/v0.8.3 | | v2.1.0 | w3cschemas/v0.9.0 | | v2.1.1 | w3cschemas/v0.9.1 | +| v2.2.0 | w3cschemas/v0.10.0 | The minor number counts **w3cschemas releases**, not go-xml ones, and two go-xml releases produced none at all. Any rule derived from the parent version diff --git a/internal/version/version.go b/internal/version/version.go index 001909eb..cf755c83 100644 --- a/internal/version/version.go +++ b/internal/version/version.go @@ -44,7 +44,7 @@ import "strings" // Between them, the constant cannot drift ahead of the changelog or behind // the tags without a red build. That is the check the original constant never // had. -const Version = "2.1.1" +const Version = "2.2.0" // IsReleaseTriple reports whether v is N.N.N with no empty component. //