Skip to content

chore: bump Discourse to 2026.9.0-latest; 2026.9.0-latest:2 → 2026.9.0-latest:3 - #5

Closed
helix-a wants to merge 1 commit into
masterfrom
next
Closed

helix-a wants to merge 1 commit into
masterfrom
next

Conversation

@helix-a

@helix-a helix-a commented Sep 7, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Pin the mutable discourse/discourse:2026.9.0-latest tag to its September 8 multi-architecture OCI index and release StartOS version 2026.9.0-latest:3.
  • Include upstream improvements to anonymous-search controls, tag localization, AI translations, login and signup routing, admin reports, composer image resizing, and data updates after code reloads.
  • Include Discourse's retirement of solved and topic-voting badges.
  • Keep PostgreSQL 18 and the bundled plugin set unchanged; the image index was verified for both amd64 and arm64.

Testing

  • Passed npm run check.
  • Not runtime-tested: upgrade an existing Discourse install with forum data to 2026.9.0-latest:3, wait for schema migration and asset compilation to finish, then confirm the service is healthy and existing topics, search, login, and administration pages load normally.
  • As an administrator, disable anonymous search and verify a signed-out user cannot search; create and delete the final localization of a tag; resize a composer image to 25%; and confirm existing badge, favorite-count, and private-message-recipient data remains current without a reload.

Merge with a merge commit — do not squash. next is long-lived: a merge commit leaves it a true ancestor of master, so it fast-forwards cleanly afterwards. A squash re-lands the same content under a new commit, so the branch is left carrying history master will never contain.

…0-latest:3

Helix-Harness: pi
Helix-Model: openai-codex/gpt-5.6-sol
@MattDHill

Copy link
Copy Markdown
Member

Closing: a nightly rebuild of an unchanged tag is not an upstream release. UPDATING.md is changing so a bump is cut only when the tag name moves, with the digest refreshed on demand before a restore.

@MattDHill MattDHill closed this Sep 8, 2026
MattDHill added a commit that referenced this pull request Sep 8, 2026
Upstream rebuilds the current tag of every release line nightly, so the
digest behind an unchanged tag moves every day. UPDATING.md told the
monitor to follow it, which produced one revision-bump PR per night (#3,
#4, #5) with nothing in it a user asked for.

The upstream version is now the tag name: a bump is cut when a new line
or point tag appears, pinning that day's index digest. An unchanged tag
is 'no changes'. The digest can still be refreshed on demand as a
revision bump, which is what a restore from a more recent main-line
instance needs — Start9's own forum included.

Moving to the stable line was considered and rejected: its current tag
is rebuilt nightly too, and it can never accept a main-line backup.
MattDHill added a commit that referenced this pull request Sep 17, 2026
`next` carried the closed #5 (a nightly-rebuild digest bump to :3) whose
`current.ts` conflicts with master's :3. Master's content wins on every file,
including the manifest digest, which stays at the September 6 pin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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