@guildofgleks/ui 21.5.1 → 21.5.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +31 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,7 +4,28 @@ All notable changes to `@guildofgleks/ui` are documented here. Format follows
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.0.0/); this project has not yet
|
|
5
5
|
reached 1.0, so breaking changes may land in minor versions.
|
|
6
6
|
|
|
7
|
-
## [21.5.
|
|
7
|
+
## [21.5.2] - 22.08.2026
|
|
8
|
+
|
|
9
|
+
Documentation only, and specifically the copy of this file that ships inside the package: 21.5.0
|
|
10
|
+
and 21.5.1 were both published while their headings still read `planned`, so the changelog in the
|
|
11
|
+
tarball described two live releases as unreleased. Nothing in the code changed — there is no
|
|
12
|
+
reason to upgrade from 21.5.1 except to get a changelog that reads correctly.
|
|
13
|
+
|
|
14
|
+
### Fixed
|
|
15
|
+
|
|
16
|
+
- **21.5.0 and 21.5.1 carry their real release dates** (21.08.2026 and 22.08.2026, from the npm
|
|
17
|
+
registry) instead of `planned`. This file is the only source that cannot drift from the package
|
|
18
|
+
it documents, because it travels inside it — which is exactly why a wrong date in it is worth a
|
|
19
|
+
patch. It is also what the documentation site renders on its releases page: that page reads
|
|
20
|
+
`node_modules/@guildofgleks/ui/CHANGELOG.md` at build time rather than any copy of its own, so
|
|
21
|
+
until this ships it shows "planned" beside the version its reader is running.
|
|
22
|
+
|
|
23
|
+
`npm run release` now refuses to publish when the top heading's version does not match
|
|
24
|
+
`package.json` or its date still says `planned`. Swapping that word for the date is a manual
|
|
25
|
+
step at the end of a long list, which is a step that gets missed — twice, here — and nothing
|
|
26
|
+
downstream could tell the difference.
|
|
27
|
+
|
|
28
|
+
## [21.5.1] - 22.08.2026
|
|
8
29
|
|
|
9
30
|
Two defects 21.5.0 shipped, both of the same shape: correct-looking CSS whose effect was cancelled
|
|
10
31
|
by something else in the box model, and neither visible to a test suite that runs without a style
|
|
@@ -58,7 +79,15 @@ a version bump with nothing to migrate.
|
|
|
58
79
|
now written down where you meet it — README's "Overlays and the viewport", `AGENTS.md`, and the
|
|
59
80
|
TSDoc of each overlay.
|
|
60
81
|
|
|
61
|
-
|
|
82
|
+
- **The package's own front page was two releases stale.** `README.md` opened with "An Angular 21
|
|
83
|
+
component library … 27 components", while `package.json`'s description had said Angular 21 and
|
|
84
|
+
22 since 21.5.0 — two files in one tarball contradicting each other. It now says 21 and 22, 29
|
|
85
|
+
components and 17 (not fifteen) directives beyond the five named ones, and mentions RTL, which
|
|
86
|
+
it never did. `AGENTS.md`'s version marker still read `21.4.4` "plus the removals already landed
|
|
87
|
+
for the unreleased 21.5.0"; it now reads 21.5.1, with the **Removed in 21.5.0** section framed as
|
|
88
|
+
what it is — a migration table for code written against 21.4.x.
|
|
89
|
+
|
|
90
|
+
## [21.5.0] - 21.08.2026
|
|
62
91
|
|
|
63
92
|
**The breaking release** — the one version consumers have to read before upgrading into. It
|
|
64
93
|
carries the removals below and the token-prefix rename (`--gog-btn-*`, `--gog-ms-*` and
|