# Fireside 0.1.0-next.5 release notes

> Fireside 0.1.0-next.5, 12 September 2026: Functions admission parity for upstream-ignored handlers. Fix a startup regression in next.4: the Functions host…

Functions admission parity for upstream-ignored handlers. Published on 12 September 2026, as a preview.

[Every release](https://firenook.dev/changelog)

Published as `@fireside-dev/cli`, before Firenook’s rename. [About the former name](https://firenook.dev/docs/help/former-name).

A newer release is out: [Firenook 0.2.0](https://firenook.dev/changelog/0.2.0), the first release for public use.

## What changed

The changes, as the release notes give them.

1. Fix a startup regression in next.4: the Functions host rejected every handler that firebase-tools 15.22.0 itself marks ignored. A published Extension function whose `extension.yaml` declares only `taskQueueTrigger` (for example `algolia/firestore-algolia-search`'s full reindex) is discovered by upstream without a trigger and ignored; the official emulator logs it and starts, next.4 failed with `discovered but not admitted`. The host now fails readiness only when upstream ignored a handler after a registration with this suite's own peers, and reports upstream-untypable handlers by identity and reason on stderr with an `ignoredCount` in the READY receipt. Those handlers still receive no deliveries, as on the official emulator.

2. Announce each completed native routing refresh on stdout after a Functions source reload (`fireside functions routing refreshed: N registered functions`); upstream `/backends` lists a new handler slightly before the native topic table is replaced.

## How it was checked

The source it was built from, the runs it passed, and how it was published.

- Pin the engine to `40c9f3f4fd32e9cc4409b14bee5ba390b1bf3c12`, the merge of [PR #30](https://github.com/firenook-dev/firenook/pull/30) on the next.4 engine.
- Recaptured the `functions-readiness-v1` oracle with the upstream-ignored scenario and archived the owned-adapter verification receipt. No dependency version, toolchain or package layout change. Prerelease on `next`; no stable or universal-compatibility claim. Private consumer acceptance evidence for the next.4 engine is not re-run for this host-level correction; the representative consumer's real configuration (three extensions, full dataset) reached readiness with a private local build of the fix before publication.

[The release on GitHub](https://github.com/firenook-dev/firenook/releases/tag/npm-v0.1.0-next.5).

## The latest is 0.2.0

The first release for public use. Install it, and read what changed on the way.

`npm install --save-dev firenook@0.2.0`

[Read the 0.2.0 notes](https://firenook.dev/changelog/0.2.0)