[claude]

Requested by Rak Ramprakash · Slack thread

Before: The published firecrawl-cli is 1.27.0, so the --sort flag for research search-papers and the created and updated dates on each row (#364) are on main but not in the npm package or the release binaries.

After: package.json carries 1.28.0, so the publish and release workflows pick up the new version. This is a minor release because #364 adds a flag.

Included since v1.27.0 (tagged at 070319b): #364, research search-papers --sort relevance|date_desc on both the keyed and keyless paths, author lists printed as names, and created and updated dates on each hit. The only file changed is package.json, as in #365. On merge, Publish to npm packs 1.28.0 and waits for approval in the release environment before publishing with the latest tag, and Release Binaries builds the platform binaries and creates the v1.28.0 GitHub release.

Checked locally: pnpm run build, pnpm run type-check, pnpm run format:check and pnpm test (904 passed, 51 skipped) all pass, and node dist/index.js --version prints 1.28.0.

---

Generated by Claude Code

---

Summary by cubic

Bumps firecrawl-cli to 1.28.0 so the npm publish and release binaries pick up the --sort flag for research search-papers and the created and updated dates on each row (#364), which are on main but missing from the published 1.27.0 release. The only file changed is package.json; on merge, the release workflows publish 1.28.0 to npm and create the v1.28.0 GitHub release.

^{Written for commit 0e6c5dc. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Bumps package.json to 1.28.0, which triggers the npm publish and release-binaries workflows to ship the accumulated CLI changes to all users.

View guided diff | Turn on auto-fix | Re-trigger cubic</sub>