Skip to content

feat: enforce owner ID requirement in mattermost connect#4

Open
scottt-shakudo wants to merge 1 commit intoShakudo-io:mainfrom
scottt-shakudo:scott1/kaji/fix-reply-all
Open

feat: enforce owner ID requirement in mattermost connect#4
scottt-shakudo wants to merge 1 commit intoShakudo-io:mainfrom
scottt-shakudo:scott1/kaji/fix-reply-all

Conversation

@scottt-shakudo
Copy link

@scottt-shakudo scottt-shakudo commented Feb 3, 2026

Added validation logic to handleConnect to check if MATTERMOST_OWNER_USER_ID is configured when MATTERMOST_REQUIRE_OWNER is set to "true". This prevents the bot from initializing without a designated owner when strict authorization is enabled.

Without this setting any client using this will respond to all messages from all users. This may be the desired behavour in some situations, hence the override.

Added validation logic to `handleConnect` to check if `MATTERMOST_OWNER_USER_ID` is configured when `MATTERMOST_REQUIRE_OWNER` is set to "true". This prevents the bot from initializing without a designated owner when strict authorization is enabled.
Copy link
Contributor

@yiran-shakudo yiran-shakudo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

yevgeniy-ds pushed a commit that referenced this pull request Feb 8, 2026
…ation posts

Bug #1: Add debug logging for reasoning parts, relax delta null check
Bug #2: Finalize stale posts with 'Completed' instead of frozen 'Processing'
Bug #3+#4: Replace soft-delete with updatePost for continuation fragments
Bug #5: Reuse compaction notification post instead of creating duplicates
Bug #6: Reset response buffers after compaction to prevent old content flash

Bumps to v0.3.76
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants