chore(release): prep 3.3.1 — ueberdb2 6.1.9 + changelog

[JohnMcLear]

Release prep for 3.3.1 (patch).

What

• Bump ueberdb2 6.1.8 → 6.1.9 in src/package.json + bin/package.json (+ lockfile)
• Add the # 3.3.1 CHANGELOG entry (required by bin/release.ts before the Release workflow can run)

Why bump ueberdb2

6.1.9 carries database-layer crash-recovery fixes:

• PostgreSQL pool errors handled + TCP keep-alive enabled (fixes Connection terminated unexpectedly with postgresql since v2.5.0 #7878)
• Redis + RethinkDB drivers attach connection-error handlers so a dropped DB connection no longer crashes the Etherpad process

Changelog coverage

Covers all commits since v3.3.0: security #7937 (GHSA-f7h5-v9hm-548j), fixes #7931/#7928/#7929, admin fix #7938 (#7935), downstream-compat CI #7923/#7924/#7927, offline-boot test #7936, dep bumps #7932/#7933/#7934, and the ueberdb2 bump.

Once this and #7938 are merged to develop and CI is green, the Release etherpad workflow will be dispatched with release_type=patch.

🤖 Generated with Claude Code

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Release 3.3.1 prep: ueberdb2 6.1.9 + changelog entry
✨ Enhancement 📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

Walkthroughs

Description

• Add CHANGELOG 3.3.1 entry required for the release workflow.
• Bump ueberdb2 to ^6.1.9 in runtime and release tooling manifests.
• Regenerate pnpm lockfile to pin ueberdb2 6.1.9 resolution.

Diagram

graph TD
  A["src/package.json"] --> C["pnpm-lock.yaml"] --> D["ueberdb2 6.1.9"] --> E{{"npm registry"}}
  B["bin/package.json"] --> C
  F[["CHANGELOG 3.3.1"]] --> G["Release workflow"]
  subgraph Legend
    direction LR
    _file["File"] ~~~ _doc[["Doc"]] ~~~ _ext{{"External"}}
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Centralize ueberdb2 version via workspace/override

• ➕ Eliminates the need to bump ueberdb2 in multiple manifests
• ➕ Reduces risk of src/bin version skew in future release preps
• ➖ Requires repository/package-manager structure changes that may not be desirable for a patch release
• ➖ May complicate tooling expectations if bin/ and src/ are intentionally decoupled

2. Generate changelog entry during release (from labels/PRs)

• ➕ Avoids manual gating failures due to missing CHANGELOG headers
• ➕ Improves consistency/formatting and reduces release-prep toil
• ➖ Non-trivial process change; requires agreeing on source-of-truth metadata
• ➖ May produce lower-quality narrative release notes without manual curation

Recommendation: For a patch release, the PR’s current approach (manual changelog entry + explicit dependency bumps in both manifests + lockfile update) is the safest and lowest-risk path. Consider workspace/override centralization or release-time changelog generation as follow-up improvements if repeated multi-manifest bumps or missing-changelog gates become a recurring friction point.

File Changes

Documentation (1)

CHANGELOG.md Add 3.3.1 release notes entry +25/-0

Add 3.3.1 release notes entry

• Introduces a new # 3.3.1 section describing security, notable fixes, CI changes, and dependency updates. This entry satisfies the release process requirement that a matching changelog section exists before dispatching the release workflow.

CHANGELOG.md

---

Other (3)

package.json Bump ueberdb2 to ^6.1.9 for release tooling +1/-1

Bump ueberdb2 to ^6.1.9 for release tooling

• Updates the ueberdb2 dependency from ^6.1.8 to ^6.1.9 in the bin/ package manifest to keep tooling aligned with the release dependency set.

bin/package.json

---

pnpm-lock.yaml Update lockfile for ueberdb2 6.1.9 resolution +7/-7

Update lockfile for ueberdb2 6.1.9 resolution

• Regenerates pnpm lock entries so both importers resolve ueberdb2 at 6.1.9, including updated package integrity and snapshot entries.

pnpm-lock.yaml

---

package.json Bump ueberdb2 to ^6.1.9 for runtime +1/-1

Bump ueberdb2 to ^6.1.9 for runtime

• Updates the runtime ueberdb2 dependency from ^6.1.8 to ^6.1.9 to pick up database crash-recovery/hardening fixes.

src/package.json

---