Release 1.6.0 - #28
Merged
Merged
Conversation
The version numbers now describe what is actually here: the shared core the browser and the desktop app both run, the installable offline site, account history and the one History page, and the legibility and keyboard work. All of that shipped after v1.5.0 and none of it was reflected in the version the shell shows. Bumped in the three places it lives: manifest.json (which the installer names release directories from), website/package.json with its lockfile, and LATEST_DESKTOP_CLIENT, which the server reports to desktop clients. bin/check-plugin.mjs now holds those three together. It has always checked the first two; the client version was the one that could drift alone, and drift is what these numbers have done here before. Proven by mutation: setting the client version back to 1.5.0 fails the check, and so does moving the manifest to 1.7.0. No behaviour changes in this commit.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
typearchy | fdcaa92 | Commit Preview URL Branch Preview URL |
Sep 20 2026, 12:13 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The version numbers now describe what is actually here. Everything from the shared core through account history, the one History page, the legibility fix and the accessibility work shipped after v1.5.0, and none of it was reflected in the version the shell shows.
Bumped in the three places the version lives:
manifest.json(the installer names release directories from it),website/package.jsonwith its lockfile, andLATEST_DESKTOP_CLIENT, which the server reports to desktop clients.bin/check-plugin.mjsnow holds all three together. It already checked the first two; the client version was the one that could drift alone, and these numbers have drifted here before. Proven by mutation: setting the client version back to 1.5.0 fails the check, and moving the manifest to 1.7.0 fails it too.Gate on this branch: engine mirrors current, all four engine tests, 60 website tests, tsc, lint and the production build. No behaviour changes.