Release 1.30.0 - #216
Merged
Merged
Conversation
Ships the tldraw 5.2.5 upgrade, so files saved by a current tldraw open, and the .tldraw messaging. Also drops a 1.29.1 entry from release/versions.json. That version was staged in b48442c and never released, and publishing 1.30.0 copies this file over the one the plugin registry reads, so the phantom would have gone out with it.
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.
Bumps the version so 1.30.0 can be released to everyone, rather than only to BRAT users as
1.30.0-alpha.1was.What ships in it:
.tldrfiles saved by a current version of tldraw open instead of failing withIncompatible schema?and an empty tab — likely closing [BUG] Can't load .tldraw files from Tldraw website. #184, Could not put content: could not migrate content #138, and the "corrupted file" report on [BUG] Failed to open "" on mobile #193.tldrawmessaging (Acknowledge .tldraw files from tldraw offline #211): opening one from tldraw offline explains why it can't be opened yet and links to the export instructions, rather than landing on Obsidian's unknown-file screennpm versioncascades the version intorelease/manifest.jsonandrelease/versions.jsonon its own — the repo has aversionlifecycle script — so those changes are mechanical.One thing that isn't mechanical
This drops a
"1.29.1"entry fromrelease/versions.json. That version was staged in b48442c and never released — there's no tag and no GitHub release for it. It matters here because releasing a non-prerelease copiesrelease/versions.jsonover the rootversions.json, which is the file the plugin registry reads, so the phantom entry would have been published. Everything in that file shares the sameminAppVersion, so it was unlikely to misresolve anyone's install, but it shouldn't go out either way.After this,
release/versions.jsonmatches the published file exactly apart from the new1.30.0line.Release plan
Merge, then Actions → Manual Release → Run workflow with
ref: main. Unlike the alpha, this path adds theversions.jsonentry and pushes the manifest commit back, which is what makes it visible to everyone on the community plugin list.Worth knowing before merging
1.30.0-alpha.1was published but, as far as I know, never installed and exercised through BRAT. So the evidence behind this release is the CI suite (8 behaviours, including opening a current.tldr, the theme, the edit round trip, view mode and embeds) plus manual checks in a scratch vault — not a soak on a real vault. Mobile is untested by anything.