# Firenook 0.2.0-next.1 release notes > Firenook 0.2.0-next.1, 19 September 2026: firenook: the project renamed, one license. The project is renamed from Fireside to Firenook; this is the first… Firenook: the project renamed, one license. Published on 19 September 2026, as a preview. `npm install --save-dev firenook@0.2.0-next.1` [Every release](https://firenook.dev/changelog) 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. The project is renamed from Fireside to Firenook; this is the first release under the new name and the minor version moves because the command and the package names change. `@fireside-dev/cli` becomes `firenook` (binary `firenook`), the platform packages `@fireside-dev/` become `@firenook/cli-`, every `FIRESIDE_*` environment variable becomes `FIRENOOK_*` (`FIRENOOK_SHUTDOWN`, `FIRENOOK_CONTROL_STDIN`, `FIRENOOK_OFFLINE`, `FIRENOOK_LOCATOR_DIR`, `FIRENOOK_FUNCTIONS_HOST_READY`, `FIRENOOK_WORKER_*`, `FIRENOOK_DEFAULT_*`, `FIRENOOK_PUBLIC_POLICY`, `FIRENOOK_PUBLICATION_POLICY`, …), the run directory `.fireside/runs` becomes `.firenook/runs`, the MCP tools `fireside_*` become `firenook_*`, and `fireside native …` becomes `firenook native …`. No alias of the old names is kept. The hub locator file (`hub-.json`), the default ports, the `firebase.json` handling and the Emulator UI asset flow are unchanged. Persisted suite state written by an earlier release is adopted in place: the store files `fireside.redb`/`fireside.wal` are renamed to `firenook.redb`/`firenook.wal` once, before the state is validated, so a `--resume-state` directory keeps its data across the upgrade (CI resumes the last engine published under the old name, `0.1.0-next.3`, with this one). 2. One license: the MIT/Apache dual license is replaced by the Apache License 2.0 alone (`LICENSE`), with a `NOTICE` file and `TRADEMARKS.md` (forks and modified builds are distributed under another name). Both files ship in every package. 3. The repository moves to `github.com/firenook-dev/firenook`; GitHub redirects the old URLs. Release history, banked benchmark results and the frozen oracle corpora keep the identifiers they were recorded and digest-pinned with (project ids such as `demo-fireside-*`), and `scripts/check-independence.mjs` now fails on any other occurrence of the former name. ## How it was checked The source it was built from, the runs it passed, and how it was published. - Pin the engine to `9d6925115e12e49524b9991f5924d112eb14ffd1`, the qualified head of [PR #58](https://github.com/firenook-dev/firenook/pull/58) (the rename) on the next.9 engine. This exact revision passed CI ([run 35445747233](https://github.com/firenook-dev/firenook/actions/runs/35445747233)) and the five-platform packed-install matrix ([run 35445747328](https://github.com/firenook-dev/firenook/actions/runs/35445747328)); a local candidate built from it passed the packed npm and Bun installs and the complete-suite smoke, and the native-upgrade verifier resumed state written by the last engine published under the old name (`0.1.0-next.3`) with it: import, in-place adoption, reopen, both browser listen modes, portable rollback. Every oracle corpus replays unchanged (Functions/Extensions 271/271, Cloud Tasks 61/61, Auth 1068 steps with 0 mismatches, Pub/Sub 916 steps with 0 mismatches). The engine is the 0.1.0-next.9 engine plus the rename, the store-file adoption and the legacy resume-token decoding; no emulator behaviour changed. [The release on GitHub](https://github.com/firenook-dev/firenook/releases/tag/npm-v0.2.0-next.1). ## 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)