Dot release docs for v11.6.2, v11.5.5, v10.11.16#8932
Dot release docs for v11.6.2, v11.5.5, v10.11.16#8932
Conversation
- Update download links in deploy-rhel.rst and deploy-tar.rst - Update server releases table in mattermost-server-releases.md - Add changelog entries in mattermost-v11-changelog.md and mattermost-v10-changelog.md - Update version-archive.rst (Enterprise and Team Edition entries) Note: SHA-256 checksums in version-archive.rst are marked TBD and need to be filled in with values from releases.mattermost.com before merging. Co-authored-by: Amy Blais <amyblais@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates Mattermost documentation to reflect the latest dot releases for v11.6.2, v11.5.5, and v10.11.16 across installation guides, release index pages, changelogs, and the version archive.
Changes:
- Bumps download links in Linux deployment guides to v11.6.2 (latest) and v10.11.16 (current ESR).
- Adds changelog entries for v11.6.2, v11.5.5, and v10.11.16.
- Updates “Server Releases” and “Version Archive” to point at the new dot releases (including SBOM links).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| source/product-overview/version-archive.rst | Updates Enterprise/Team archive entries to v11.6.2, v11.5.5, and v10.11.16 download + signature + SBOM links. |
| source/product-overview/mattermost-v11-changelog.md | Adds entries for 11.6.2 and 11.5.5. |
| source/product-overview/mattermost-v10-changelog.md | Adds entry for 10.11.16 (ESR). |
| source/product-overview/mattermost-server-releases.md | Updates latest-release table download and SBOM links to the new dot releases. |
| source/deployment-guide/server/linux/deploy-tar.rst | Updates wget URLs for latest and ESR tarball downloads. |
| source/deployment-guide/server/linux/deploy-rhel.rst | Updates wget URLs for latest and ESR tarball downloads. |
|
Newest code from mattermost has been published to preview environment for Git SHA 5a4909f |
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR updates documentation to reflect dot releases 11.6.2, 11.5.5, and 10.11.16: new changelog entries and upgrade notes, updated download/SBOM URLs and checksums (marked TBD) in the version archive and releases table, and updated wget commands in Linux deployment guides. ChangesMattermost Server Release Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
🚥 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
source/deployment-guide/server/linux/deploy-rhel.rst (1)
38-54:⚠️ Potential issue | 🔴 CriticalThe 11.6.2 release tarball URLs return HTTP 403 (Forbidden) and will block admins at the download step.
The documented URLs for version 11.6.2 (
https://releases.mattermost.com/11.6.2/mattermost-11.6.2-linux-amd64.tar.gz) are not publicly accessible. Verify that the release assets exist at the paths specified in the documentation, or update the version numbers to point to accessible releases.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/deployment-guide/server/linux/deploy-rhel.rst` around lines 38 - 54, The example download URLs under "Step 3: Download the latest Mattermost Server tarball" reference a 11.6.2 asset that returns HTTP 403; update the documentation to point to an accessible release or to a stable canonical URL (e.g., use the actual released version that exists or a /latest/ redirect) by replacing the hard-coded 11.6.2 and 10.11.16 example links with verified, publicly accessible tarball URLs (or a variable placeholder such as {VERSION} with guidance to choose a published release), and confirm the links used in the "Latest release" and "Current ESR" code blocks are reachable.source/product-overview/mattermost-server-releases.md (1)
18-31:⚠️ Potential issue | 🟠 MajorConfirm download link path for v11.6.2—currently returning HTTP 403.
The primary download link for v11.6.2 (
https://releases.mattermost.com/11.6.2/mattermost-11.6.2-linux-amd64.tar.gz) is inaccessible with a 403 Forbidden response. Since this is the "Latest releases" table on the landing page, a broken download link directly blocks users from obtaining the software. Verify that the release has been published to the correct path and that the URL is accurate. This may also affect the v11.5.5 and v10.11.16 download links and their corresponding SBOM URLs.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-server-releases.md` around lines 18 - 31, The "Latest releases" table row for v11.6 (the line containing the download URL string "https://releases.mattermost.com/11.6.2/mattermost-11.6.2-linux-amd64.tar.gz" in the "v11.6" table entry) points to a URL returning 403; verify the release was published to that exact path and fix the entry by updating the download URL to the correct published path (or remove/replace it with an alternate working link), and while you're there validate the paired SBOM links and the download URLs for v11.5 (the "v11.5" entry) and v10.11 (the "v10.11" entry) return HTTP 200; commit the corrected link(s) in the "Latest releases" table so the landing page uses only accessible URLs.
🤖 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/version-archive.rst`:
- Around line 482-492: The SHA-256 checksum fields for "Mattermost Team Edition
v11.6.2" and "Mattermost Team Edition v11.5.5" currently read "TBD" and must be
replaced with the authoritative checksums; locate the checksum lines under the
headings "Mattermost Team Edition v11.6.2" and "Mattermost Team Edition v11.5.5"
(the lines that read "SHA-256 Checksum: ``TBD``") and substitute the correct
SHA-256 values from the release artifacts before merging/publishing so the
integrity verification workflow can run.
- Around line 14-23: The SHA-256 Checksum fields for "Mattermost Enterprise
Edition v11.6.2" and "v11.5.5" in version-archive.rst currently read "TBD" and
must be replaced with the authoritative checksums from the actual release
artifacts; locate the two checksum lines labeled "SHA-256 Checksum: ``TBD``"
under the blocks for "v11.6.2" and "v11.5.5" and update each to the exact
SHA-256 hex string for the corresponding tarball (the same artifact URL shown on
each block) prior to merging/publishing so the published archive allows proper
verification.
- Around line 522-526: The Team Edition v10.11.16 ESR entry currently has
"SHA-256 Checksum: ``TBD``"; replace that placeholder with the authoritative
SHA-256 hex value taken from the official release artifact (the 10.11.16 Linux
tarball) and keep the existing inline literal formatting (backticks) so the line
reads e.g. SHA-256 Checksum: ``<actual-checksum>``; update the same line in the
version-archive.rst Team Edition v10.11.16 entry and verify the checksum matches
the release artifact before merging.
- Around line 54-58: The SHA-256 placeholder for the Enterprise v10.11.16 ESR
entry must be replaced with the actual checksum from the release artifact;
locate the published tarball named "mattermost-10.11.16-linux-amd64.tar.gz" (the
same URL in the Download/Release lines) and update the "SHA-256 Checksum:
``TBD``" line to the real hex checksum string before merging so the
version-archive entry for "Mattermost Enterprise Edition v10.11.16 *Extended
Support Release (ESR)*" contains the correct integrity value.
---
Outside diff comments:
In `@source/deployment-guide/server/linux/deploy-rhel.rst`:
- Around line 38-54: The example download URLs under "Step 3: Download the
latest Mattermost Server tarball" reference a 11.6.2 asset that returns HTTP
403; update the documentation to point to an accessible release or to a stable
canonical URL (e.g., use the actual released version that exists or a /latest/
redirect) by replacing the hard-coded 11.6.2 and 10.11.16 example links with
verified, publicly accessible tarball URLs (or a variable placeholder such as
{VERSION} with guidance to choose a published release), and confirm the links
used in the "Latest release" and "Current ESR" code blocks are reachable.
In `@source/product-overview/mattermost-server-releases.md`:
- Around line 18-31: The "Latest releases" table row for v11.6 (the line
containing the download URL string
"https://releases.mattermost.com/11.6.2/mattermost-11.6.2-linux-amd64.tar.gz" in
the "v11.6" table entry) points to a URL returning 403; verify the release was
published to that exact path and fix the entry by updating the download URL to
the correct published path (or remove/replace it with an alternate working
link), and while you're there validate the paired SBOM links and the download
URLs for v11.5 (the "v11.5" entry) and v10.11 (the "v10.11" entry) return HTTP
200; commit the corrected link(s) in the "Latest releases" table so the landing
page uses only accessible URLs.
🪄 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: c81a323d-eb72-4bb2-b01d-5bc7d5320307
📒 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
|
Newest code from mattermost has been published to preview environment for Git SHA 9a880be |
|
Newest code from mattermost has been published to preview environment for Git SHA c26c48e |
|
Newest code from mattermost has been published to preview environment for Git SHA dd7bf0c |
|
Newest code from mattermost has been published to preview environment for Git SHA 49b3c61 |
|
Newest code from mattermost has been published to preview environment for Git SHA 317c669 |
|
Newest code from mattermost has been published to preview environment for Git SHA 5d7ad32 |
|
Newest code from mattermost has been published to preview environment for Git SHA b5eae3b |
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 83: Update the malformed release header "- **10.11.16, released **" to
include the actual release date in YYYY-MM-DD format and remove the extra space
inside the emphasis, e.g. replace it with "- **10.11.16, released 2024-05-04**"
(use the correct date for the release) so the bold emphasis is well-formed and
MD037 is resolved.
In `@source/product-overview/mattermost-v11-changelog.md`:
- Line 19: Replace the placeholder "released " in the bold release headings with
actual release dates (format YYYY-MM-DD): update the string "**11.6.2, released
**" to "**11.6.2, released YYYY-MM-DD**" and likewise update the other
occurrence at the later heading (the bold line around line 159) to include its
correct date; ensure there are no extra spaces inside the bold markers so the
MD037 warning is resolved.
🪄 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: 87efd1fd-97c4-4717-a1e5-8ca1600bff56
📒 Files selected for processing (3)
source/administration-guide/upgrade/important-upgrade-notes.rstsource/product-overview/mattermost-v10-changelog.mdsource/product-overview/mattermost-v11-changelog.md
✅ Files skipped from review due to trivial changes (1)
- source/administration-guide/upgrade/important-upgrade-notes.rst
|
Newest code from mattermost has been published to preview environment for Git SHA 6a44fdf |
|
Newest code from mattermost has been published to preview environment for Git SHA 3e65ac9 |
|
Newest code from mattermost has been published to preview environment for Git SHA c0c436c |
Closes #8931
Generated with Claude Code