Open
Conversation
- Update deploy-rhel.rst and deploy-tar.rst download links - Update mattermost-server-releases.md table entries - Add v11.6.1, v11.5.4, v11.4.5 entries to v11 changelog - Add v10.11.15 entry to v10 changelog - Update version-archive.rst (Enterprise + Team Edition) for all 4 releases Note: SHA-256 checksums in version-archive.rst are marked TBD and need to be filled in with the actual values from the release binaries. Co-authored-by: Amy Blais <amyblais@users.noreply.github.com>
Contributor
📝 WalkthroughWalkthroughDocumentation updates for dot releases v11.6.1, v11.5.4, v11.4.5 and v10.11.15: bumped download URLs and artifact links, added patch changelog entries (including security fixes, plugin updates, integration URL validation notes, and Go 1.25.8 upgrade), and marked checksums as TBD in the version archive. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related issues
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA abd0fb7 |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Mattermost documentation set to reflect the latest dot releases for the v11.6, v11.5, v11.4 trains and the v10.11 ESR train, aligning download/install instructions and release notes with the new patch versions.
Changes:
- Update Linux deployment guides (
deploy-tar.rst,deploy-rhel.rst) to download v11.6.1 and v10.11.15. - Add dot-release entries to the v11 and v10 changelogs for v11.6.1, v11.5.4, v11.4.5, and v10.11.15.
- Update the server releases table and version archive to reference the new patch versions.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| source/product-overview/version-archive.rst | Updates the “latest” archive entries to the new dot releases for Enterprise and Team editions. |
| source/product-overview/mattermost-v11-changelog.md | Adds entries for v11.6.1, v11.5.4, and v11.4.5. |
| source/product-overview/mattermost-v10-changelog.md | Adds an entry for v10.11.15 (ESR). |
| source/product-overview/mattermost-server-releases.md | Updates “Latest releases” download/SBOM links to the newest patch versions. |
| source/deployment-guide/server/linux/deploy-tar.rst | Updates tarball download commands for Latest release and Current ESR. |
| source/deployment-guide/server/linux/deploy-rhel.rst | Updates tarball download commands for Latest release and Current ESR. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA f626f65 |
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA 44f0af4 |
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA 640846d |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@source/product-overview/mattermost-v10-changelog.md`:
- Line 79: The changelog entry for version "10.11.15" is missing its release
date; update the markdown line that currently reads "**10.11.15, released **" to
include the actual release date (e.g. "released Month D, YYYY" or the project’s
standard date format) so the entry becomes "**10.11.15, released <date>**".
Ensure the format matches other entries in the file and commit the updated line.
In `@source/product-overview/mattermost-v11-changelog.md`:
- Line 15: Update the three dot-release headings to include their full release
dates and remove the trailing space before the closing bold markers: replace
`**11.6.1, released **`, `**11.5.4, released **`, and `**11.4.5, released **`
with the format `**11.6.1, released YYYY-MM-DD**`, `**11.5.4, released
YYYY-MM-DD**`, and `**11.4.5, released YYYY-MM-DD**` (substitute the correct
dates) so the versions (11.6.1, 11.5.4, 11.4.5) follow the established
`YYYY-MM-DD` pattern and no extra space remains before `**`.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 619c5bc0-a0a6-4fb7-9000-1ee0c32e6b99
📒 Files selected for processing (6)
source/deployment-guide/server/linux/deploy-rhel.rstsource/deployment-guide/server/linux/deploy-tar.rstsource/product-overview/mattermost-server-releases.mdsource/product-overview/mattermost-v10-changelog.mdsource/product-overview/mattermost-v11-changelog.mdsource/product-overview/version-archive.rst
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA 036606d |
amyblais
added
Do Not Merge
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (1)
source/product-overview/mattermost-v11-changelog.md (1)
15-15:⚠️ Potential issue | 🟡 MinorFill in release dates and remove trailing emphasis-space in dot-release headings.
Line 15, Line 149, and Line 276 still use
releasedwith no date and include a trailing space before**, which also triggers MD037.As per coding guidelines, “Flag awkward phrasing, punctuation mistakes, tense shifts, and terminology inconsistencies in documentation”.📝 Minimal fix pattern
-- **11.6.1, released ** +- **11.6.1, released YYYY-MM-DD** -- **11.5.4, released ** +- **11.5.4, released YYYY-MM-DD** -- **11.4.5, released ** +- **11.4.5, released YYYY-MM-DD**Also applies to: 149-149, 276-276
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-v11-changelog.md` at line 15, Update the dot-release headings that read like "**11.6.1, released **" (and the similar headings for the other dot-releases) to include the actual release date and remove the trailing space before the closing bold markup so they become e.g. "**11.6.1, released 2024-03-12**"; locate the headings by searching for the literal strings like "11.6.1, released" and replace each with the correct date and no extra space before the final "**".
🧹 Nitpick comments (1)
source/product-overview/mattermost-v11-changelog.md (1)
16-16: Use repo-internal doc links instead of hardcodeddocs.mattermost.comURLs in new entries.The new “Upgrading” links should follow repo-appropriate internal Markdown link style for docs pages.
Based on learnings, “Internal links to Mattermost docs should use repo-appropriate internal link syntax instead of hardcoded `https://docs.mattermost.com/...` URLs. Provide a minimal diff (suggested change) when the fix is straightforward and the correct target is clear.”🔧 Minimal diff
- [Upgrading](https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html) + [Upgrading](../upgrade/upgrading-mattermost-server.md)Also applies to: 150-150, 277-277
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-v11-changelog.md` at line 16, Replace hardcoded external docs URLs with the repo's internal Markdown doc links: update the "Upgrading" link that currently points to https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html to use the repository's internal docs link syntax for the upgrade page (match how other docs pages are linked in this repo), and similarly swap the hardcoded https://mattermost.com/security-updates/ and https://mattermost.com/security-vulnerability-report/ links to their internal doc equivalents; apply the same replacements for the other occurrences mentioned (the entries at the other two locations).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@source/product-overview/mattermost-v11-changelog.md`:
- Line 15: Update the dot-release headings that read like "**11.6.1, released
**" (and the similar headings for the other dot-releases) to include the actual
release date and remove the trailing space before the closing bold markup so
they become e.g. "**11.6.1, released 2024-03-12**"; locate the headings by
searching for the literal strings like "11.6.1, released" and replace each with
the correct date and no extra space before the final "**".
---
Nitpick comments:
In `@source/product-overview/mattermost-v11-changelog.md`:
- Line 16: Replace hardcoded external docs URLs with the repo's internal
Markdown doc links: update the "Upgrading" link that currently points to
https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html to use the
repository's internal docs link syntax for the upgrade page (match how other
docs pages are linked in this repo), and similarly swap the hardcoded
https://mattermost.com/security-updates/ and
https://mattermost.com/security-vulnerability-report/ links to their internal
doc equivalents; apply the same replacements for the other occurrences mentioned
(the entries at the other two locations).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4ec108c4-ec1f-4b03-b372-439ee7d1667b
📒 Files selected for processing (1)
source/product-overview/mattermost-v11-changelog.md
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA db8786c |
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA 3ebd263 |
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA 5bb3ca7 |
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (2)
source/product-overview/mattermost-v11-changelog.md (1)
15-15:⚠️ Potential issue | 🟡 MinorComplete the dot-release dates and remove emphasis-marker spacing.
These three entries are still incomplete and trigger markdown lint (
MD037) because of the trailing space before**. Please use the samereleased YYYY-MM-DDformat already used throughout the page.📝 Minimal suggested diff
-- **11.6.1, released ** +- **11.6.1, released YYYY-MM-DD** -- **11.5.4, released ** +- **11.5.4, released YYYY-MM-DD** -- **11.4.5, released ** +- **11.4.5, released YYYY-MM-DD**As per coding guidelines, “Watch for formatting drift in headings, lists, callouts, code blocks, tables, emphasis, and capitalization that do not match repo conventions.”
Also applies to: 149-149, 279-279
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-v11-changelog.md` at line 15, The heading entry "**11.6.1, released **" is missing the release date and has an extra space before the closing emphasis marker; update it to follow the repo convention "11.6.1, released YYYY-MM-DD" (no trailing space inside the ** markers) and apply the same fix to the other incomplete releases noted (the other "11.x.x" entries flagged), ensuring each uses the exact "released YYYY-MM-DD" format and no extra spacing inside the bold markers.source/product-overview/mattermost-v10-changelog.md (1)
79-79:⚠️ Potential issue | 🟡 MinorAdd the missing release date and fix malformed bold text.
**10.11.15, released **is incomplete and triggers invalid emphasis formatting. Please fill in the date before merge.Suggested minimal diff
-- **10.11.15, released ** +- **10.11.15, released YYYY-MM-DD**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-v10-changelog.md` at line 79, The release heading contains malformed bold markup "**10.11.15, released **" and is missing the release date; update that line in the markdown (the string "**10.11.15, released **") to include the actual release date and proper bolding (e.g., "**10.11.15, released YYYY-MM-DD**") so the emphasis is valid and the date is filled in before merging.
🧹 Nitpick comments (1)
source/product-overview/mattermost-v10-changelog.md (1)
80-80: Use repo-internal link syntax for Mattermost docs links.This changed line uses a hardcoded
docs.mattermost.comURL for an internal docs page. Please switch to the repo’s internal link format used for docs sources.As per coding guidelines, "Internal links to Mattermost docs should use repo-appropriate internal link syntax instead of hardcoded
https://docs.mattermost.com/...URLs."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-v10-changelog.md` at line 80, The line uses hardcoded external URLs for internal docs—replace the full "https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html" link (the anchor text "Upgrading") and the "https://mattermost.com/security-updates/" link (anchor "security updates page") with the repo’s internal link syntax used elsewhere in the docs so they resolve internally; keep the visible anchor text unchanged and ensure link targets point to the corresponding internal docs pages (also update the adjacent "Mattermost Responsible Disclosure Policy" link if it’s internal) so the markup matches other files’ internal-link format.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@source/product-overview/mattermost-v10-changelog.md`:
- Line 79: The release heading contains malformed bold markup "**10.11.15,
released **" and is missing the release date; update that line in the markdown
(the string "**10.11.15, released **") to include the actual release date and
proper bolding (e.g., "**10.11.15, released YYYY-MM-DD**") so the emphasis is
valid and the date is filled in before merging.
In `@source/product-overview/mattermost-v11-changelog.md`:
- Line 15: The heading entry "**11.6.1, released **" is missing the release date
and has an extra space before the closing emphasis marker; update it to follow
the repo convention "11.6.1, released YYYY-MM-DD" (no trailing space inside the
** markers) and apply the same fix to the other incomplete releases noted (the
other "11.x.x" entries flagged), ensuring each uses the exact "released
YYYY-MM-DD" format and no extra spacing inside the bold markers.
---
Nitpick comments:
In `@source/product-overview/mattermost-v10-changelog.md`:
- Line 80: The line uses hardcoded external URLs for internal docs—replace the
full "https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html" link
(the anchor text "Upgrading") and the "https://mattermost.com/security-updates/"
link (anchor "security updates page") with the repo’s internal link syntax used
elsewhere in the docs so they resolve internally; keep the visible anchor text
unchanged and ensure link targets point to the corresponding internal docs pages
(also update the adjacent "Mattermost Responsible Disclosure Policy" link if
it’s internal) so the markup matches other files’ internal-link format.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3403a820-27bc-43a0-a265-3b520d13c2cf
📒 Files selected for processing (3)
source/product-overview/mattermost-v10-changelog.mdsource/product-overview/mattermost-v11-changelog.mdsource/product-overview/version-archive.rst
🚧 Files skipped from review as they are similar to previous changes (1)
- source/product-overview/version-archive.rst
Contributor
|
Newest code from mattermost has been published to preview environment for Git SHA ae9ec10 |
esethna
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release dates to be added when ready.
Resolves #8905
Generated with Claude Code