Releases: triptechtravel/slackbuzz-cli
Releases · triptechtravel/slackbuzz-cli
v0.10.4
v0.10.3
Changelog
v0.10.2
v0.10.1
v0.10.0
v0.9.5
v0.9.4
Documentation
- README: Added
sendshortcut,doctorcommand, self-DM behavior docs, and updated required scopes - SKILL.md: Documented self-DM via bot behavior
- docs/commands.md: Added
sendshortcut anddoctorcommand reference, self-DM behavior - docs/getting-started.md: Added doctor verification step, uses
sendshortcut - docs/ai-agents.md: Added agent mode (
SLACKBUZZ_AGENT=1) and diagnostics sections - docs/security.md: Updated required scopes, noted separate bot/user identity storage
Tests
TestLooksLikeUser— validates DM target detection for @NAMEs, user IDs, channel IDsTestIsMissingScopeError— validates missing_scope error detection (direct, wrapped, contained)TestFormatResolveError— validates actionable error messages for channel resolution failuresTestFormatSendError— validates context-aware error messages for DM vs channel send failuresTestAuthConfigRoundTrip— validates bot/user identity fields persist through save/loadTestAuthConfigClear— validates all fields cleared including bot identityTestAuthConfigBotAndUserSeparate— validates bot and user info don't overwrite each other in auth.yml
v0.9.3
Bug Fixes
- Auth storage: Bot and user identity are now stored separately in keyring and auth.yml. Previously,
StoreUserInfowas called for both token types, so whichever was stored last would overwrite the other — causing self-DM detection andResolveUserID()to return the wrong identity. - Self-DM detection: Now uses
client.AuthUserID()(liveauth.testcall) instead of reading stored user info, making it reliable regardless of storage state. - ResolveUserID: Only uses the user token now (not bot token), since bot token returns the bot's identity, not the human's.
Internal
- New keyring keys:
bot_user_id,bot_user_namefor bot identity - New auth.yml fields:
bot_user_id,bot_user_name StoreBotUserInfo()/GetBotUserInfo()functions- Login and app create flows now store bot vs user info to the correct keys
- Tests for separate bot/user info storage
v0.9.2
Fix: add im:write to bot scopes so the bot can open DM conversations for self-DM. You need to add im:write to your bot token scopes in Slack app settings and re-install.
v0.9.1
Fix: re-open DM channel via bot client for self-DM. The bot needs its own DM channel ID — the one from the user token's conversations.open isn't valid for the bot client.