As I mentioned in the standup there's a slight issue with VS Code releases. We usually do a release, after that I create a VS Code extension release (bump the package version, add the changelog). Which means that if we then do a hotfix it does not have these changes as they were added after a deploy.
So for this hotfix I did the following:
checked out hotfixes branch
created a new branch
bumped package.json version and added change log
committed it to the branch
created a vs code extension package and published it
I don't think it makes sense to merge it back to hotfixes branch as it would just create a new deploy with no changes.
Next I created this PR to get the changes to main.
went to main
created this branch from there and cherry picked the commit created above
Change Type
[ ] sdk — Changes the tldraw SDK
[ ] dotcom — Changes the tldraw.com web app
[ ] docs — Changes to the documentation, examples, or templates.
[x] vs code — Changes to the vscode plugin
[ ] internal — Does not affect user-facing stuff
[ ] bugfix — Bug fix
[ ] feature — New feature
[ ] improvement — Improving existing features
[x] chore — Updating dependencies, other boring stuff
[ ] galaxy brain — Architectural changes
[ ] tests — Changes to any test code
[ ] tools — Changes to infrastructure, CI, internal scripts, debugging tools, etc.
VS Code version bump.
As I mentioned in the standup there's a slight issue with VS Code releases. We usually do a release, after that I create a VS Code extension release (bump the package version, add the changelog). Which means that if we then do a hotfix it does not have these changes as they were added after a deploy.
So for this hotfix I did the following:
hotfixes
branchNext I created this PR to get the changes to
main
.main
Change Type
sdk
— Changes the tldraw SDKdotcom
— Changes the tldraw.com web appdocs
— Changes to the documentation, examples, or templates.vs code
— Changes to the vscode plugininternal
— Does not affect user-facing stuffbugfix
— Bug fixfeature
— New featureimprovement
— Improving existing featureschore
— Updating dependencies, other boring stuffgalaxy brain
— Architectural changestests
— Changes to any test codetools
— Changes to infrastructure, CI, internal scripts, debugging tools, etc.dunno
— I don't know