From 4a64a50c3730c709e30d518ca15abb78f3c5a733 Mon Sep 17 00:00:00 2001 From: Imani Manyara <19682005+imanimanyara@users.noreply.github.com> Date: Mon, 16 Nov 2026 15:12:26 -0500 Subject: [PATCH] Fold the documentation corrections into 0.1.0 v0.1.0 moves again to carry PR 27, on the owner's go; the release notes come from the [0.1.0] section. --- CHANGELOG.md | 15 ++++++--------- docs/upgrading.md | 8 ++++---- 2 files changed, 10 insertions(+), 13 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f949e9f..863c8a1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,15 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ## [Unreleased] -### Fixed - -- Documentation checked page by page against the code, and 30 statements corrected: stale counts - (18 commands, 29 `SettingsException` subclasses, six models), features described as unreleased - that ship (approvals, re-encryption, persisted configuration), global overrides reaching owners - only when the setting inherits, encrypted history payloads answered as `null`, recipe snippets - that missed a gate, an import or a `register()` call, and the stated reason SQL Server is not - supported. `make-store --connection`'s help now names every shared table it creates. - ## [0.1.0] - 2026-11-16 The first public release. `Added` describes the package; `Changed`, `Removed`, `Fixed` and @@ -203,6 +194,12 @@ Each was removed before the first tag; none was in a tagged release. (`[Mail-Host, mail_host] -> mail_host`) before anything is written, in a dry run and when applied. Input without collisions imports exactly as before. `ImportedKeys::values()` applies the same check for a custom importer. +- Documentation checked page by page against the code, and 30 statements corrected: stale counts + (18 commands, 29 `SettingsException` subclasses, six models), features described as unreleased + that ship (approvals, re-encryption, persisted configuration), global overrides reaching owners + only when the setting inherits, encrypted history payloads answered as `null`, recipe snippets + that missed a gate, an import or a `register()` call, and the stated reason SQL Server is not + supported. `make-store --connection`'s help now names every shared table it creates. ### Security diff --git a/docs/upgrading.md b/docs/upgrading.md index 2ced6d8..d41c168 100644 --- a/docs/upgrading.md +++ b/docs/upgrading.md @@ -12,10 +12,10 @@ what to do, and this page lists the steps. ## If you installed 0.1.0 or 0.1.1 before 2026-11-16 The first `v0.1.0` (2026-11-11) and `v0.1.1` (2026-11-14) were withdrawn, and the history was -squashed into a single `v0.1.0`, published 2026-11-14, that holds everything both carried, plus runtime -overrides. That tag was moved on 2026-11-16 to add `SettingsMisuse` and `SettingsError`. Composer -caches an archive per version name, so an install from an earlier tag keeps the old code until the -cache is cleared: +squashed into a single `v0.1.0`, published 2026-11-14, that holds everything both carried, plus +runtime overrides. That tag was moved on 2026-11-16 to add `SettingsMisuse` and `SettingsError`, and +again the same day to carry corrected documentation. Composer caches an archive per version name, so +an install from an earlier tag keeps the old code until the cache is cleared: ```bash composer clear-cache && composer update laranail/settings