Skip to content

chore: move the published version to 0.18.3 - #75

Merged
yusuf-gundogdu merged 1 commit into
mainfrom
surum/libredb-studio-0.18.3
Oct 17, 2026
Merged

yusuf-gundogdu merged 1 commit into
mainfrom
surum/libredb-studio-0.18.3

Conversation

@yusuf-gundogdu

Copy link
Copy Markdown
Member

The site has advertised 0.18.2 since 11 October. The footer chip reads studio 0.18.2 on every page, and the deploy snippet hands visitors that tag.

Two pins move:

  • site.config.json version, which feeds footer.versionChip
  • src/data/compose.ts tag, the tag shown in the compose snippet

Its why line moves with it because the claim was re-checked rather than assumed: the Dockerfile at 0.18.3 still builds the runner FROM node:26.10.0-trixie-slim, the same as at 0.18.2.

Five other mentions of 0.18.2 are left alone on purpose. They state when something was verified or what happened at that version, so bumping them would turn a true sentence into a false one:

  • src/data/features.ts and src/data/security.ts — "re-verified at/against 0.18.2"
  • src/data/code-signing.ts — a commit list
  • src/data/deploy-channels.ts — what channels.yaml held at 0.18.2
  • docs/DECISIONS.md — "At 0.18.2 four of its comments were false"

@yusuf-gundogdu
yusuf-gundogdu merged commit d2a4eba into main Oct 17, 2026
5 checks passed
@yusuf-gundogdu
yusuf-gundogdu deleted the surum/libredb-studio-0.18.3 branch October 17, 2026 10:32
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