Skip to content

4.0.0 release checklist #979

Open
Open

Description

@ismisepaul

Tracks what has to land before tagging 4.0.0, and the release steps from docs/releasing.md. Everything listed here is in the Next Release Backlog column of project 11.

4.0.0 goals: dependencies maintained and free of known CVEs, no known security vulnerabilities in the platform (the levels stay vulnerable on purpose), no known bugs that exhaust the database or stop the platform working, and the new unified mobile app.

Before merging: PRs labelled Needs Manual Testing must be tested by hand from their branch first. Each one's description starts with the branch to check out, the steps, and what counts as broken. Record the result as a comment on the PR.

Blockers

Security (platform)

CVEs and supported versions

Database exhaustion and broken functionality

Mobile

Release pipeline and tests

Moved out of 4.0.0

These don't block the release, and they no longer ship with it.

#1084 (a single main branch) also waits for 4.1.0, so 4.0.0 and 4.0.1 follow the dev to master steps in docs/releasing.md.

Not in 4.0.0: production hardening of the Docker Compose quick start

The Docker Compose setup is a quick start, not a production deployment (#1020). Hardening it stays in the backlog, and the README says what to change for a real deployment: #814 (runtime database configuration), #988 (MongoDB without authentication), #987 (unused mongod.conf). The exception is #991, the image shipping the build's TLS key, which is fixed for 4.0.0 by #1036: each container now generates its own certificate on first start.

Release steps

  • Check open Dependabot alerts and the WAR's runtime jars for known CVEs
  • Upgrade notes in the release: Java 17, Tomcat 11 (recreate the conf volume), MariaDB 12.3, MongoDB 8.0, SAML on pac4j
  • PR to dev: pom.xml 4.0.0-SNAPSHOT → 4.0.0
  • Release PR dev → master, merged with a merge commit
  • Tag 4.0.0 on the merge commit (admin), and check the Docker Hub images are published
  • GitHub release with release notes and the mobile APK
  • Publish GHSA-m4gj-wcx8-jjr7
  • PR to dev: pom.xml → 4.1.0-SNAPSHOT

🤖 Generated with Claude Code

Activity

  1. moved this from Backlog to Next Release Backlog in Security Shepherdon Oct 24, 2026
  2. added this to the 4.0.0 milestone on Oct 24, 2026
  3. ismisepaul commented on Oct 25, 2026

    @ismisepaul
    MemberAuthor

    Ticked #950, fixed by #1017 (the release workflow publishes again), and #961, fixed by #1036 (the TLS certificate is now generated when the container starts, with the correct locality). #1036 also fixed the TLS half of #991, so the published image no longer ships a private key. The database half continues in #814.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions