Repository navigation
Bump github.com/mattermost/mattermost/server/public from 0.1.21 to 0.3.0 - #676
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>
|
Ah thought it ended up being the usual dist action failing, I'll push a new commit with linter fixes 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)
📝 WalkthroughWalkthroughThis PR updates Go to 1.25.8 and bumps multiple dependencies, including a major version lift for the Mattermost server/public package to v0.3.0. The only functional code change is a single-line update in ChangesMattermost Dependency Update and API Attachment Type
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 PR introduces a significant dependency bump (Mattermost server/public v0.1.21 → v0.3.0) alongside multiple other dependency updates, and includes a code change in OAuth error handling. While the direct code modification is localized to error notification messaging, the broad dependency updates increase the blast radius and potential for regressions.
Regression Risk: The primary concern is the larger version bump to
github.com/mattermost/mattermost/server/publicwhich could introduce breaking API changes in an upstream library. The secondary concern is the change to error notification handling in the GitLab OAuth flow, though this is limited to message formatting. Linter errors that required follow-up fixes suggest potential compatibility issues. Multiple transitive dependency changes increase the surface area for unexpected interactions.QA Recommendation: Comprehensive manual QA testing of the GitLab OAuth connection flow (successful connections and failure scenarios) is recommended. Additionally, smoke testing of core authentication and notification flows should be performed to validate dependency compatibility. The broad nature of the dependency updates warrants testing beyond just the modified code path. Skipping manual QA would pose moderate risk given the authentication-related changes and upstream library version bump.