Skip to content

Release Canasta 3.5.20 - #691

Merged
cicalese merged 1 commit into
masterfrom
release/3.5.20
Aug 1, 2026
Merged

Release Canasta 3.5.20#691
cicalese merged 1 commit into
masterfrom
release/3.5.20

Conversation

@cicalese

@cicalese cicalese commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the base image pin to CanastaBase 1.3.19 and VERSION to 3.5.20.

CanastaBase 1.3.19 serves /server-status to loopback over IPv6 and points the image's HEALTHCHECK at 127.0.0.1 numerically. The <If> guard had matched REMOTE_ADDR against 127.0.0.1 alone, so wherever localhost resolves to ::1 first the healthcheck reached MediaWiki instead of the status handler and failed permanently rather than retrying over IPv4.

The CrawlerProtection update named in the release note arrives via its own PR, #690 (CrawlerProtection 1.7.0). Rebased onto current master, so this PR carries only the release mechanics.

Refs #689

@cicalese
cicalese marked this pull request as draft August 1, 2026 13:35
@cicalese

cicalese commented Aug 1, 2026

Copy link
Copy Markdown
Contributor Author

Blocked on #690. The 3.5.20 tag is emitted once, on the master push whose diff touches VERSION, and it is immutable — so if this merges first, canasta:3.5.20 is built from a tree still pinning Recommended Revisions 344e7b3 (CrawlerProtection 1.5.0) and permanently disagrees with its own release note. Merge #690 first; marking ready once it lands.

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown

🐳 The image based on 004d9be3 commit has been built with 1.43.9-20260801-691 tag as ghcr.io/canastawiki/canasta:1.43.9-20260801-691

Bumps the base image pin to CanastaBase 1.3.19 and VERSION to 3.5.20.

CanastaBase 1.3.19 serves /server-status to loopback over IPv6 and points the
image's HEALTHCHECK at 127.0.0.1 numerically. The <If> guard had matched
REMOTE_ADDR against 127.0.0.1 alone, so wherever localhost resolves to ::1 the
healthcheck reached MediaWiki instead of the status handler and failed
permanently.

The CrawlerProtection update named in the release note arrives via its own PR.
Rebased onto current master, so this PR carries only the release mechanics.
@cicalese
cicalese marked this pull request as ready for review August 1, 2026 14:36
@cicalese
cicalese merged commit 39d1e45 into master Aug 1, 2026
3 checks passed
@cicalese
cicalese deleted the release/3.5.20 branch August 1, 2026 14:41
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