Bump github.com/mattermost/mattermost/server/public from 0.1.21 to 0.3.0#1019
Conversation
Bumps [github.com/mattermost/mattermost/server/public](https://github.com/mattermost/mattermost) from 0.1.21 to 0.3.0. - [Release notes](https://github.com/mattermost/mattermost/releases) - [Changelog](https://github.com/mattermost/mattermost/blob/master/CHANGELOG.md) - [Commits](mattermost/mattermost@server/public/v0.1.21...server/public/v0.3.0) --- updated-dependencies: - dependency-name: github.com/mattermost/mattermost/server/public dependency-version: 0.3.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Hello @dependabot[bot], Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughGo version and multiple direct and indirect dependencies are updated in ChangesDependency and compatibility updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bumps github.com/mattermost/mattermost/server/public from 0.1.21 to 0.3.0.
Commits
9b01e40Move password hashers from server/v8 to server/public to fix module layering ...50f31aeMm 66662 bump dependencies (#35849)4d20645Inline mattermost-govet into the monorepo (#35869)eb8310asimplify CODEOWNERS (#35770)aaefd41MM-68120 - Use repo checkout for build files in server-ci-artifacts (#35842)d001251disable burn on read posts on shared channels (#35460)f4d1abeMM-68140: Validate post read access before rewrite thread context (#35864)47d2c60Docs impact fixes (#35877)2550ecdci: post success to required e2e status contexts when no relevant changes (#3...3e2c3f7fix: prevent sql.DB connectionCleaner race and harden flaky tests (#35891)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Change Impact: 🟡 Medium
Reasoning: This Dependabot PR updates the core
mattermost/server/publicdependency from v0.1.21 to v0.3.0 (a significant minor version bump with potential API changes) and modifies the authentication flow to use a newer Mattermost API type. While the direct code change is minimal (one-line attachment type replacement inconnectUserToGitHub), it touches a critical user-facing authentication completion path and introduces multiple upstream dependency changes that could trigger unexpected behaviors.Regression Risk: The shift from
SlackAttachmenttoMessageAttachmentin the post-OAuth direct message flow affects how user notifications are rendered after GitHub authentication completes. The v0.3.0 dependency bump may introduce breaking changes or incompatibilities not immediately visible. Multiple indirect dependencies are updated simultaneously (golang.org/x/* versions, google.golang.org packages), increasing the surface area for potential regressions. The OAuth connection flow is user-critical and any rendering or delivery issues would directly impact authentication completion experience.QA Recommendation: Manual testing of the GitHub OAuth flow is recommended—specifically: (1) verify that the post-OAuth direct message is properly delivered and rendered to users upon successful authentication, (2) test both success and error message paths (the
MessageAttachmentchange applies to the error case), and (3) validate that message formatting and styling display correctly in Mattermost clients. Testing cannot be safely skipped given the authentication path criticality; however, a focused regression test on the OAuth DM delivery flow would be sufficient rather than comprehensive re-testing of all plugin features.Generated by CodeRabbitAI