Skip to content

chore(release): 2.2.0 - #23

Merged
Flosk6 merged 3 commits into
masterfrom
release/2.2.0
Oct 10, 2026
Merged

Flosk6 merged 3 commits into
masterfrom
release/2.2.0

Conversation

@Flosk6

@Flosk6 Flosk6 commented Oct 10, 2026

Copy link
Copy Markdown
Owner

Release 2.2.0: the security fixes of the 2026-10-08 review (#18, #19, #20, #21), and the documentation that https://spawner.run is built from, with Traefik 3.7 (#22).

  • CHANGELOG.md: the 2.2.0 section, which becomes the release notes, with what to do when upgrading from 2.1.0 (install.sh --upgrade once on the server for the firewall, DNS providers lego v5 dropped).
  • scripts/release.sh 2.2.0: the version of every package.json, of server.json and the default version of install.sh. The script now sets server.json too: the workflow already published it at the tag's version.
  • The digests of Postgres and Traefik in install.sh are current (docker buildx imagetools inspect: postgres:17-alpine unchanged, traefik:v3.7 still 3.7.14).

Merge with a merge commit: the tag v2.2.0 points at chore(release): 2.2.0 (ff29444), and the Release workflow refuses a tag that is not on master. The tag is pushed once this is merged.

After the release: the site's repository variable SPAWNER_DOCS_REF is emptied, so that https://spawner.run follows the release again, and its comparison page is marked as checked against 2.2.0.

release.sh sets the version of server.json, and of its npm package, with the package.json files: the workflow already publishes it at the version of the tag, and the file in the repository now says the same.
@Flosk6
Flosk6 merged commit 61eb29f into master Oct 10, 2026
4 checks passed
@Flosk6
Flosk6 deleted the release/2.2.0 branch October 10, 2026 13:10

This branch was successfully deployed

1 active deployment
release — ff29444f Deployed Oct 10, 2026 by Flosk6 via GitHub release #5
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.

1 participant