release: 1.23.0 - #207
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump to publish the new
setupsubcommands (#206) to npm.Merge after #206 — merging this triggers
publish.yml(npm publish of whatever is onmain) andrelease-binaries.yml, so #206 must be onmainfirst 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)--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-clito 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 skillsonly; nowsetup core,setup build, andsetup workflows(withsetup skillskept as an alias forcore).setup <skill-name>; thefirecrawl-prefix is optional (e.g.,setup developer-index).--browseror interactive confirm, and prints a one-line hint in non-interactive runs; never blocks agents/CI.Review and rollout:
main; otherwise 1.23.0 will publish without the new subcommands.publish.yml(npm publish ofmain) andrelease-binaries.yml.Written for commit c5bd8e9. Summary will update on new commits.