[github-actions]

nano_kit

3.0.0 (2026-11-10)

⚠ BREAKING CHANGES

• query: keys(), which iterates over every registered cache key builder, is
  renamed to eachKeyBuilder(), and keys now names the client extension that adds
  eachKey(): keys(Key => invalidate(Key)) becomes eachKeyBuilder(Key => invalidate(Key)).
• agera,kida: MaybeAccessorValue is removed from agera, use SignalishValue.
  ValueOrAccessor, AnyValueOrAccessor, ValueOrSignal and ValueOrWritableSignal are
  removed from kida, and with it from @nano_kit/store, which re-exports it: use
  Signalish and AnySignalish, or T | WritableSignal<T> where only a writable signal fits.
• intl: for a message function, like one of params, plural or match, the
  function of wrap() receives (message, values, locale), not (values, message, locale):
  (place, message) => message(place) becomes (message, place) => message(place). The
  value form keeps (message, locale).

Features

• agera,kida: drop the type aliases deprecated by the Signalish rename (#356) (2568ccb), references #210
• intl: pass the message to the function of wrap() before the values of its call (#357) (daff68b)
• query: pick the cached keys of a builder by their parameters with the keys() extension, and rename the old keys() to eachKeyBuilder() (#355) (87970c1)

Bug Fixes

• query: ask again in the browser for a key the server was still loading (#351) (6d74bab)
• query: ask for a failed key again when it is read again (#350) (ec69fef)
• query: keep cache writes made while fetchNext loads a page (#346) (646ee41)
• query: keep data written with $data while a key loads for the first time (#349) (bd46da4)
• query: keep entity updates when fetchNext loads a page (#347) (a3dd4e1)
• query: keep the data and the loaded pages when retryOnError retries (#354) (4783420)
• query: refetch every loaded page when an infinite query is revalidated (#353) (023aaaf)

agera

3.0.0 (2026-11-10)

⚠ BREAKING CHANGES

• MaybeAccessorValue is removed from agera, use SignalishValue.
  ValueOrAccessor, AnyValueOrAccessor, ValueOrSignal and ValueOrWritableSignal are
  removed from kida, and with it from @nano_kit/store, which re-exports it: use
  Signalish and AnySignalish, or T | WritableSignal<T> where only a writable signal fits.

Features

• drop the type aliases deprecated by the Signalish rename (#356) (2568ccb), references #210

@nano_kit/intl

3.0.0 (2026-11-10)

⚠ BREAKING CHANGES

• for a message function, like one of params, plural or match, the
  function of wrap() receives (message, values, locale), not (values, message, locale):
  (place, message) => message(place) becomes (message, place) => message(place). The
  value form keeps (message, locale).

Features

• pass the message to the function of wrap() before the values of its call (#357) (daff68b)

kida

3.0.0 (2026-11-10)

⚠ BREAKING CHANGES

• MaybeAccessorValue is removed from agera, use SignalishValue.
  ValueOrAccessor, AnyValueOrAccessor, ValueOrSignal and ValueOrWritableSignal are
  removed from kida, and with it from @nano_kit/store, which re-exports it: use
  Signalish and AnySignalish, or T | WritableSignal<T> where only a writable signal fits.

Features

• drop the type aliases deprecated by the Signalish rename (#356) (2568ccb), references #210

@nano_kit/query

3.0.0 (2026-11-10)

⚠ BREAKING CHANGES

• keys(), which iterates over every registered cache key builder, is
  renamed to eachKeyBuilder(), and keys now names the client extension that adds
  eachKey(): keys(Key => invalidate(Key)) becomes eachKeyBuilder(Key => invalidate(Key)).

Features

• pick the cached keys of a builder by their parameters with the keys() extension, and rename the old keys() to eachKeyBuilder() (#355) (87970c1)

Bug Fixes

• ask again in the browser for a key the server was still loading (#351) (6d74bab)
• ask for a failed key again when it is read again (#350) (ec69fef)
• keep cache writes made while fetchNext loads a page (#346) (646ee41)
• keep data written with $data while a key loads for the first time (#349) (bd46da4)
• keep entity updates when fetchNext loads a page (#347) (a3dd4e1)
• keep the data and the loaded pages when retryOnError retries (#354) (4783420)
• refetch every loaded page when an infinite query is revalidated (#353) (023aaaf)

---

This PR was generated with simple-release.

📄 Cheatsheet

You can configure the bot's behavior through a pull request comment using the !simple-release/set-options command.

Command Format

!simple-release/set-options

```json
{
  "bump": {}
}
```

Useful Parameters

The options shape the pull request generation, so the bump ones matter here. Release-time options like publish belong in the config file.

Parameter	Type	Description
version	string	Force set specific version
as	'major' | 'minor' | 'patch' | 'prerelease'	Release type. prerelease keeps the type derived from the commits and makes the version a prerelease
prerelease	string	Pre-release identifier (e.g., "alpha", "beta")
firstRelease	boolean	Whether this is the first release
skip	boolean	Skip version bump
byProject	Record<string, object>	Per-project bump options for monorepos

Usage Examples

Force specific version

!simple-release/set-options

```json
{
  "bump": {
    "version": "2.0.0"
  }
}
```

Force major bump

!simple-release/set-options

```json
{
  "bump": {
    "as": "major"
  }
}
```

Create alpha pre-release

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "alpha"
  }
}
```

Custom Changelog Preamble

You can add custom markdown to the top of the changelog (right after the version header) using the !simple-release/set-preamble command. The markdown after the command line becomes the preamble. Start its headings at ### — the level of the generated changelog sections like ### Features.

!simple-release/set-preamble

### What's new?

- The website was completely redesigned
- The new API gives you awesome possibilities

In a monorepo, pass the full package name after the command to target a single package's changelog. Wrap the name in backticks so GitHub keeps it as text instead of a mention:

!simple-release/set-preamble `@your-org/core`

### Core changes

- New plugin system

Use one comment per package, plus one without a name for the whole release.

Access Restrictions

The commands can only be used by users with permissions:

• repository owner
• organization member
• collaborator

Notes

• The last comment with !simple-release/set-options command takes priority
• The last !simple-release/set-preamble comment per package takes priority
• JSON must be valid, otherwise the set-options command will be ignored
• Parameters apply only to the current release execution
• The commands can be updated by editing the comment or adding a new one