1.7 KiB
Publishing
This document mainly exists so I (Bauke) remember how to go about publishing Love since it's a little complicated for certain platforms.
To update the version of a theme, use yarn versioning
.
Published to platforms
The following sections assume you have previously published a version, but are starting from a completely fresh repository.
Visual Studio Code
- Run
yarn build
(oryarn build:vscode
). - Change into the VS Code source directory (
cd source/vscode/
). - Run
yarn package
to create the.vsix
package. - Head to the Marketplace Manage Extensions page.
- Click on the
...
next to the current version and click onUpdate
. - Upload the
.vsix
that was created in step 3.
Open VSX
Love is also published to open-vsx.org, with the ovsx CLI. To publish it, use yarn package
to package it with VSCE and then publish the resulting .vsix
file.
An access token is also required, defined as OVSX_PAT
. For example, to publish version 0.1.4, the following commands would be used:
yarn package
to create the.vsix
package (if it doesn't already exist).OVSX_PAT=<token> yarn ovsx publish love-0.1.4.vsix
.
Published to the website
The following integrations aren't yet/can't be published to platforms, so mostly no special procedure needs to happen. They are just built and served on the website directly.
- Firefox (if updated, the links need to be updated on the website too, may get published to AMO).
- Kitty.
- Sublime Text (may get published at some point).
- Tauon.