Skip to content

[25.11] mattermost, mattermostLatest: 10.11.15 / 11.5.3 -> 10.11.17 / 11.7.0 #520738

Draft
numinit wants to merge 1 commit into
NixOS:release-25.11from
numinit:for-25-11/mattermost/10.11.17
Draft

[25.11] mattermost, mattermostLatest: 10.11.15 / 11.5.3 -> 10.11.17 / 11.7.0 #520738
numinit wants to merge 1 commit into
NixOS:release-25.11from
numinit:for-25-11/mattermost/10.11.17

Conversation

@numinit
Copy link
Copy Markdown
Contributor

@numinit numinit commented May 16, 2026 •
edited
Loading

Security release. https://docs.mattermost.com/product-overview/mattermost-v10-changelog.html#release-v10-11-extended-support-release

See also #520723

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

@numinit numinit added the 1.severity: security Issues which raise a security issue, or PRs that fix one label May 16, 2026
nixpkgs-commit-check[bot]
nixpkgs-commit-check Bot requested changes May 16, 2026
View reviewed changes
Copy link
Copy Markdown

@nixpkgs-commit-check nixpkgs-commit-check Bot left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This report is automatically generated by the PR / Check / cherry-pick CI workflow.

Some of the commits in this PR require the author's and reviewer's attention.

Please follow the backporting guidelines and cherry-pick with the -x flag.
This requires changes to the unstable master and staging branches first, before backporting them.

Occasionally, commits are not cherry-picked at all, for example when updating minor versions of packages which have already advanced to the next major on unstable.
These commits can optionally be marked with a Not-cherry-picked-because: <reason> footer.

If you need to merge this PR despite the warnings, please dismiss this review shortly before merging.

Warning

Couldn't locate the cherry-picked commit's hash in the commit message of 8a434d1.

Hint: The full diffs are also available in the runner logs with slightly better highlighting.

@nixpkgs-ci nixpkgs-ci Bot requested review from Kranzes, mgdelacroix and ryantm May 16, 2026 07:35
@nixpkgs-ci nixpkgs-ci Bot added 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". 4.workflow: backport This targets a stable branch labels May 16, 2026
@numinit numinit marked this pull request as draft May 16, 2026 08:00
@nixpkgs-ci nixpkgs-ci Bot removed the 2.status: merge-bot eligible This PR can be merged by commenting "@NixOS/nixpkgs-merge-bot merge". label May 16, 2026
@numinit numinit force-pushed the for-25-11/mattermost/10.11.17 branch from c145ffc to 8a434d1 Compare May 16, 2026 08:26
@nixpkgs-ci nixpkgs-ci Bot removed the 8.has: package (update) This PR updates a package to a newer version label May 16, 2026
@numinit
Copy link
Copy Markdown
Contributor Author

numinit commented May 16, 2026

Tracking this upstream, NixOS tests are failing due to bad migration numbering: mattermost/mattermost#36594

@numinit numinit changed the title [25.11] mattermost: 10.11.15 -> 10.11.17 [25.11] mattermost, mattermostLatest: 10.11.15 / 11.5.3 -> 10.11.17 / 11.7.0 May 16, 2026
@numinit
Copy link
Copy Markdown
Contributor Author

numinit commented May 16, 2026

Ugh, I don't really want to push forward past 10.11.15 on second thought, because 10.11.16 is where they added two incompatible migrations that cause upgrades to fail, and they screwed up the versioning on top of it. I'm glad I wrote those tests now. We'll see what upstream says.

@numinit
Copy link
Copy Markdown
Contributor Author

numinit commented May 16, 2026

I guess one potential option is going to 10.11.17 and reverting the patch. It is just one commit causing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nixpkgs-commit-check nixpkgs-commit-check[bot] nixpkgs-commit-check[bot] requested changes

@Kranzes Kranzes Awaiting requested review from Kranzes

@mgdelacroix mgdelacroix Awaiting requested review from mgdelacroix

@ryantm ryantm Awaiting requested review from ryantm

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 4.workflow: backport This targets a stable branch 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@numinit