release: 1.23.0
Merged
ER
2mo ago+1+1+0123456789-1-1-0123456789
Version bump to publish the new setup subcommands (#206) to npm.
Merge after #206 — merging this triggers publish.yml (npm publish of whatever is on main) and release-binaries.yml, so #206 must be on main first or 1.23.0 ships without the new subcommands.
New in 1.23.0:
firecrawl setup core/setup build/setup workflows— one command per skill family (setup skillsstays as an alias forcore)firecrawl setup <skill-name>— install any single catalog skill;firecrawl-prefix optional (e.g.setup developer-index)- Post-install auth offer: silent when a key exists, browser login via
--browseror interactive confirm, one-line hint in non-interactive runs (never blocks agents/CI)
🤖 Generated with Claude Code
Summary by cubic
Release 1.23.0 of firecrawl-cli to ship new setup subcommands and a non‑blocking post‑install auth flow. This PR triggers npm publish, so merge order matters.
-
Behavior changes in 1.23.0:
- Setup commands: previously
setup skillsonly; nowsetup core,setup build, andsetup workflows(withsetup skillskept as an alias forcore). - Single-skill install: add
setup <skill-name>; thefirecrawl-prefix is optional (e.g.,setup developer-index). - Post-install auth: previously could prompt and block; now silent if a key exists, supports optional browser login via
--browseror interactive confirm, and prints a one-line hint in non-interactive runs; never blocks agents/CI.
- Setup commands: previously
-
Review and rollout:
- Merge only after #206 is on
main; otherwise 1.23.0 will publish without the new subcommands. - This PR only bumps the version; merging triggers
publish.yml(npm publish ofmain) andrelease-binaries.yml.
- Merge only after #206 is on