From 2b7588797190e0572cc4a55a33cf3376a2fcc444 Mon Sep 17 00:00:00 2001 From: Komol Nath Roy Date: Sun, 1 Nov 2026 06:28:24 -0500 Subject: [PATCH] release: v2.1.1 --- 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 fb7a321f..63d9558b 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.1.1 — 2026-11-01 Memory and CPU fixes from go-xmlsec's measurements against v2.1.0. No API change; output is byte-identical. diff --git a/RELEASE.md b/RELEASE.md index fca51f9f..03ced756 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -227,6 +227,7 @@ one**, and the workflow does not try to derive it: | v2.0.2 | w3cschemas/v0.8.2 (tagged by hand: the tag message had no `w3cschemas:` line) | | v2.0.3 | w3cschemas/v0.8.3 | | v2.1.0 | w3cschemas/v0.9.0 | +| v2.1.1 | w3cschemas/v0.9.1 | 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 dc772b1c..001909eb 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.0" +const Version = "2.1.1" // IsReleaseTriple reports whether v is N.N.N with no empty component. //