Conversation
- Add v2.40.0 changelog entry with placeholder content - Move v2.40 from future releases to latest releases table in mobile releases page Co-authored-by: Amy Blais <amyblais@users.noreply.github.com>
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdded Mattermost Mobile App v2.40 to the Latest releases with links, dates (Released 2026-05-15, Support Ends 2026-06-15) and compatible server refs; removed v2.40 from Future, added v2.46 and adjusted v2.45/v2.44 rows; added a v2.40.0 entry to the mobile changelog with requirements, improvements, bug fixes, and known issues. ChangesMobile release and changelog updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 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 |
There was a problem hiding this comment.
Pull request overview
Adds documentation entries for the Mattermost Mobile v2.40 release across the mobile changelog and the mobile releases index to support the planned May 2026 release cycle.
Changes:
- Added a new v2.40.0 section to the Mobile Apps Changelog.
- Added v2.40 to the “Latest releases” table and removed it from the “Future releases” table.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
source/product-overview/mobile-app-changelog.md |
Adds a new 2.40.0 changelog section (date, compatibility notes, placeholders). |
source/product-overview/mattermost-mobile-releases.md |
Promotes v2.40 into the latest releases table with links and compatibility refs. |
|
Newest code from mattermost has been published to preview environment for Git SHA 080bfb7 |
|
Newest code from mattermost has been published to preview environment for Git SHA 0f71d90 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
Newest code from mattermost has been published to preview environment for Git SHA 465cb76 |
|
Newest code from mattermost has been published to preview environment for Git SHA e0b40c5 |
amyblais
added
1: Dev Review
amyblais
requested review from
Combs7th,
asaadmahmood,
crspeller,
devinbinnie,
esethna and
larkox
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
source/product-overview/mattermost-mobile-releases.md (1)
14-14:⚠️ Potential issue | 🟡 MinorReplace hardcoded docs URL with internal link syntax.
The hardcoded
https://docs.mattermost.com/...URL should be replaced with repo-appropriate internal link syntax for maintainability and to ensure links remain valid across environments.🔗 Suggested fix
Assuming the target section has a reference label in
mattermost-server-releases.md, replace the hardcoded URL with a{ref}link:-We strongly recommend using the latest mobile app release available that contains the latest security fixes and user experience enhancements. Mobile app releases are compatible with and tested against [supported Mattermost server and extended support releases](https://docs.mattermost.com/product-overview/mattermost-server-releases.html#latest-releases). +We strongly recommend using the latest mobile app release available that contains the latest security fixes and user experience enhancements. Mobile app releases are compatible with and tested against {ref}`supported Mattermost server and extended support releases <server-latest-releases>`.Note: Verify the actual reference label in
mattermost-server-releases.mdand adjust accordingly.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-mobile-releases.md` at line 14, Replace the hardcoded external URL "https://docs.mattermost.com/product-overview/mattermost-server-releases.html#latest-releases" in source/product-overview/mattermost-mobile-releases.md with the repo's internal link syntax (use the {ref} style) pointing to the corresponding section in mattermost-server-releases.md; locate the sentence containing that URL, swap the absolute link for the internal {ref} label that matches the "latest-releases" section (verify and adjust the reference label name in mattermost-server-releases.md if needed), and ensure the surrounding Markdown remains valid and builds correctly.
🧹 Nitpick comments (2)
source/product-overview/mobile-app-changelog.md (1)
27-27: Use standard protocol notation and inline code for the literalFor consistency and clarity, format this as
HTTP/1.1(with inline code) instead of plainHTTP1.1.Suggested minimal diff
- - The pre-auth secret header name is now always retrieved in lowercase to support HTTP1.1. + - The pre-auth secret header name is now always retrieved in lowercase to support `HTTP/1.1`.As per coding guidelines: "Use inline code for commands, paths, config keys, environment variables, ports, and literal values."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mobile-app-changelog.md` at line 27, Update the changelog line that currently reads "The pre-auth secret header name is now always retrieved in lowercase to support HTTP1.1." to use standard protocol notation and inline code formatting: change "HTTP1.1" to "`HTTP/1.1`" so the literal protocol is consistently represented as inline code in the mobile-app-changelog.md content.source/product-overview/mattermost-mobile-releases.md (1)
69-71: Remove extra trailing spaces for table formatting consistency.Lines 69-71 contain extra trailing spaces before the closing pipe character that are inconsistent with the formatting used in the rest of the Future releases table (lines 72-74). While this doesn't affect the rendered output, it creates unnecessary visual inconsistency in the source.
🧹 Suggested formatting cleanup
-| v2.46 | Releasing: 2026-11-16<br/>Support Ends: 2026-12-15 | v11.13, v11.12, v11.11, v11.7 | -| v2.45 | Releasing: 2026-10-16<br/>Support Ends: 2026-11-15 | v11.12, v11.11, v11.10, v11.7 | -| v2.44 | Releasing: 2026-09-16<br/>Support Ends: 2026-10-15 | v11.11, v11.10, v11.9, v11.7 | +| v2.46 | Releasing: 2026-11-16<br/>Support Ends: 2026-12-15 | v11.13, v11.12, v11.11, v11.7 | +| v2.45 | Releasing: 2026-10-16<br/>Support Ends: 2026-11-15 | v11.12, v11.11, v11.10, v11.7 | +| v2.44 | Releasing: 2026-09-16<br/>Support Ends: 2026-10-15 | v11.11, v11.10, v11.9, v11.7 |As per coding guidelines: "Match the local table pattern already used by the page."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@source/product-overview/mattermost-mobile-releases.md` around lines 69 - 71, The table rows for v2.46, v2.45, and v2.44 have extra trailing spaces before the closing pipe; edit those rows (the lines containing "v2.46", "v2.45", "v2.44") and remove the trailing spaces so the cell contents end immediately before the "|" to match the rest of the Future releases table formatting.
🤖 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/mobile-app-changelog.md`:
- Line 30: The sentence currently reads “an "Message not viewable" error”;
change the article to “a" so it reads “a "Message not viewable" error” in the
mobile app changelog entry (the line containing the permalink/channel fix text)
to correct the grammatical article before the quoted error string.
- Line 15: Replace the hardcoded docs URL in the sentence containing "Extended
Support Release" (the link pointing to
https://docs.mattermost.com/product-overview/release-policy.html#extended-support-releases)
with the repository's internal docs link syntax (use the repo-style link or the
{ref} stable label for the ESR release policy) so the markdown uses the internal
link format instead of the external https://docs.mattermost.com/... URL.
---
Outside diff comments:
In `@source/product-overview/mattermost-mobile-releases.md`:
- Line 14: Replace the hardcoded external URL
"https://docs.mattermost.com/product-overview/mattermost-server-releases.html#latest-releases"
in source/product-overview/mattermost-mobile-releases.md with the repo's
internal link syntax (use the {ref} style) pointing to the corresponding section
in mattermost-server-releases.md; locate the sentence containing that URL, swap
the absolute link for the internal {ref} label that matches the
"latest-releases" section (verify and adjust the reference label name in
mattermost-server-releases.md if needed), and ensure the surrounding Markdown
remains valid and builds correctly.
---
Nitpick comments:
In `@source/product-overview/mattermost-mobile-releases.md`:
- Around line 69-71: The table rows for v2.46, v2.45, and v2.44 have extra
trailing spaces before the closing pipe; edit those rows (the lines containing
"v2.46", "v2.45", "v2.44") and remove the trailing spaces so the cell contents
end immediately before the "|" to match the rest of the Future releases table
formatting.
In `@source/product-overview/mobile-app-changelog.md`:
- Line 27: Update the changelog line that currently reads "The pre-auth secret
header name is now always retrieved in lowercase to support HTTP1.1." to use
standard protocol notation and inline code formatting: change "HTTP1.1" to
"`HTTP/1.1`" so the literal protocol is consistently represented as inline code
in the mobile-app-changelog.md content.
🪄 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: c6a905e0-bdee-4739-8e06-ca151f47a936
📒 Files selected for processing (2)
source/product-overview/mattermost-mobile-releases.mdsource/product-overview/mobile-app-changelog.md
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
|
Newest code from mattermost has been published to preview environment for Git SHA 4bd9952 |
|
Newest code from mattermost has been published to preview environment for Git SHA 587666b |
|
Newest code from mattermost has been published to preview environment for Git SHA d03ee67 |
|
Newest code from mattermost has been published to preview environment for Git SHA 6a350b7 |
|
Newest code from mattermost has been published to preview environment for Git SHA 4350970 |
|
Newest code from mattermost has been published to preview environment for Git SHA eab2964 |
|
Newest code from mattermost has been published to preview environment for Git SHA 1c466c3 |
|
Newest code from mattermost has been published to preview environment for Git SHA 601ee5e |
|
Newest code from mattermost has been published to preview environment for Git SHA 8288fbc |
|
Newest code from mattermost has been published to preview environment for Git SHA bb22320 |
|
Newest code from mattermost has been published to preview environment for Git SHA bd1301c |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@source/product-overview/mobile-app-changelog.md`:
- Line 30: Update the release note sentence that reads "The pre-auth secret
header name is now always retrieved in lowercase to support HTTP1.1." to use the
standard protocol notation "HTTP/1.1" (i.e., replace "HTTP1.1" with "HTTP/1.1")
so the sentence reads "...to support HTTP/1.1."
🪄 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: 554d6b5d-26a6-44cf-bf85-de454b488349
📒 Files selected for processing (1)
source/product-overview/mobile-app-changelog.md
|
Newest code from mattermost has been published to preview environment for Git SHA 7b7b7d2 |
Changelog file
Resolves #8898
Generated with Claude Code