1.8 KiB
1.8 KiB
Changelog
Unreleased
0.1.0 — 2025-12-05
Added
whoamicommand works with both GraphQL cookies and Sweetistics API keys.- Firefox cookie extraction (
--firefox-profile) alongside existing Chrome/env/CLI credential paths. - Sweetistics client
getCurrentUserwith POST→GET fallback for deployments that disallow POST. - Colorized help banner and example block;
pnpm birdbuilds then runs the CLI; no subcommand shows help. - JSON5 config files (
~/.config/bird/config.json5,./.birdrc.json5) for defaults like engine and browser profile. - Config toggles to disable cookie sources (
allowChrome,allowFirefox) and default transport nowgraphqlwith Firefox as preferred cookie source. - Conversation commands:
threadandreplies, plussearchandmentionsconvenience helpers. - Sweetistics transport for all commands (tweet, reply, read, thread, replies, search) with automatic 15s timeouts and media uploads (images or single video).
- Sweetistics conversation fetch now forces fresh data (
force=true) to bypass cache forthread/replies. - CI workflow on push/PR (Node 22, pnpm 10, Go stable) running
pnpm test.
Changed
- Default option resolution now honors config files (project then global) before env/CLI overrides.
whoaminow prefers Sweetistics when an API key is present; otherwise uses Twitter cookies.- Sweetistics media uploads use the Sweetistics engine only; GraphQL mode rejects mixed media.
Fixed
- Fallback to scraping the authenticated settings page when Twitter account APIs return 404, so
whoamistill resolves the user. - Sweetistics calls now time out after 15s to avoid hanging CLI commands when the API is slow or unresponsive.
- Sweetistics tweeting now supports media uploads (images or single video) via new CLI
--media/--altflags. - Coverage raised above 70% via new cookie and conversation tests.