Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Fixed

- When install refuses over a same-named table, its message now names the fix that needs no
config file, `LARANAIL_SETTINGS_TABLE_PREFIX`, and the publish command for renaming single
tables; it used to point at config keys in a file that had not been published yet. The
installation guide says the same, warns that a partly published config replaces the whole
`tables` array, and lists `sync-definitions` after `migrate`.

## [0.1.0] - 2026-11-16

The first public release. `Added` describes the package; `Changed`, `Removed`, `Fixed` and
Expand Down Expand Up @@ -208,6 +200,11 @@ Each was removed before the first tag; none was in a tagged release.
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.
- When install refuses over a same-named table, its message now names the fix that needs no
config file, `LARANAIL_SETTINGS_TABLE_PREFIX`, and the publish command for renaming single
tables; it used to point at config keys in a file that had not been published yet. The
installation guide says the same, warns that a partly published config replaces the whole
`tables` array, and lists `sync-definitions` after `migrate`.

### Security

Expand Down
5 changes: 3 additions & 2 deletions docs/upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,9 @@ what to do, and this page lists the steps.
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`, 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:
twice more the same day to carry corrected documentation and clearer install guidance. 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
Expand Down
Loading