Skip to content

chore(ci): refresh MongoDB version support matrix MONGOSH-3283 - #2783

Merged
ivandevp merged 2 commits into
mainfrom
MONGOSH-3283-version-support
Jul 23, 2026
Merged

chore(ci): refresh MongoDB version support matrix MONGOSH-3283#2783
ivandevp merged 2 commits into
mainfrom
MONGOSH-3283-version-support

Conversation

@ivandevp

@ivandevp ivandevp commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

MONGOSH-3283

Refreshes the MongoDB server version support matrix used for testing:

  • Add 9.0 (9.0.0-rc0) community + enterprise to the matrix, mirroring how 8.3 was covered during its pre-GA window. Since 9.0 does not publish an Ubuntu 20.04 build, its linux variants run on ubuntu2204-small — the same handling already used for the latest variant.
  • Promote 8.3 from 8.3.0-rc3 to the GA 8.3.x series, and reconcile the e2e spec (was pinned to 8.3.0-rc5) to 8.3.x.
  • Drop 4.2 — it is >3 years past its 2023-04 EOL per the platform support policy. Removed the now-dead 4.2-specific continue guards in the unit-test build-variant generator.
  • Regenerated .evergreen.yml.

Validated with a full unit-test patch across the new/changed variants — all green after pinning 9.0 linux to Ubuntu 22.04.

Follow-up (not in this PR): bump 90xc/90xe from 9.0.0-rc0 to 9.0.x once 9.0 GAs.

Add 9.0 (9.0.0-rc0) community + enterprise to the test matrix, promote 8.3
from 8.3.0-rc3 to the GA 8.3.x series, and drop 4.2 (>3 years past its
2023-04 EOL per the platform support policy).

9.0 does not publish an Ubuntu 20.04 build, so its linux variants run on
ubuntu2204-small, matching the existing handling for the `latest` variant.
Also reconcile the e2e 8.3 spec (was pinned to 8.3.0-rc5) to 8.3.x.
@ivandevp
ivandevp requested a review from a team as a code owner July 22, 2026 21:43
@ivandevp
ivandevp requested a review from nbbeeken July 22, 2026 21:43

@nbbeeken nbbeeken left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Changes lgtm!! ✅ let's wait on the CI to finish all things and restart any setup failures if you see them, even if they're unrelated-ly flaky (which we should fix) we'll want to make sure we get a green run on the server upgrades.

@ivandevp

Copy link
Copy Markdown
Collaborator Author

CI is still green 🚀

@ivandevp
ivandevp merged commit 5c7f48f into main Jul 23, 2026
158 checks passed
@ivandevp
ivandevp deleted the MONGOSH-3283-version-support branch July 23, 2026 10:45
ivandevp added a commit that referenced this pull request Jul 30, 2026
…#2786)

* feat(build): publish mongosh artifacts to 9.0 server PPA MONGOSH-3438

Add MongoDB 9.0 as a target for Linux/PPA package publishing, mirroring
the 8.3.0 configuration:
- add '9.0.0' to SupportedServerVersion and SERVER_WITH_PPAS (same distro
  set as 8.3.0; all distros already present in config/repo-config.yml)
- add the server-9.0 notary signing key mapping in barque
- add expected 9.0 publish URLs to the barque spec

The 9.0 integration test matrix was already added in #2783 (MONGOSH-3283).

Note: actual publishing depends on the external server-9.0 notary key and
9.0 apt/yum repos existing on the build side; to be confirmed before release.

* fix(build): correct 9.0 PPA platform support MONGOSH-3438

Address review feedback: the 9.0 target platform list differs from the
8.3 template it was copied from.

- add ubuntu2604 (Ubuntu 26.04, codename "resolute") and suse16 (SUSE 16)
  as new PPARepository targets, including config/repo-config.yml entries
  (org + enterprise) and computePublishedPackageUrl / getReposAndArch wiring
- add suse16 + ubuntu2604 to the 9.0.0 PPA target set
- drop ubuntu2004 (Ubuntu 20.04) from 9.0.0 — not supported for server 9.0+

Codenames/paths verified against the live repo.mongodb.org /
repo.mongodb.com listings (dists/resolute and zypper/suse/16 exist).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants