Skip to content

Commit

Permalink
feat/vscode: update the release instructions in the editors/vscode/RE…
Browse files Browse the repository at this point in the history
…LEASE.md file
  • Loading branch information
Alidra committed Apr 5, 2024
1 parent 3b3608c commit 5627a71
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion editors/vscode/RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,18 @@
TODO list for a new release on the VSCode Marketplace
-----------------------------------------------------
**Release from pipeline**

See the details [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension).
The github DICD pipeline detects the existance of a new version of the Lambdapi extension for Vscode based on the `version` field in the `editors/vscode/package.json` file and publishes it on the Marketplace.

Please note that a valid Azure Personal Access Token (PAT) is required for this operation. This PAT must be saved in the `PAT` environment variable as described [here](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions).

If the pipeline fails at publishing the extension, it may be due to the PAT being expired.
Please generate a new one on [Azure](https://dev.azure.com/lambdapi/) and update the `PAT` env variable value as described in the link above.

**manual release**

Though it is not recommanded, it is still possible to manually publish a new version on the marketplace as described bellow
(See the details [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)).

- Check the rendering of README.md in some [Markdown viewer](https://codebeautify.org/markdown-viewer). It will be displayed in VSCode by going to extensions
(Ctrl+Shift+X) and by clicking on lambdapi.
Expand Down

0 comments on commit 5627a71

Please sign in to comment.