Best practice for releasing a deno package on GitHub
Is there a best practice for the release process of a Deno library on GitHub? I use semantic-release for node libraries.
Automating the release & (publishing to jsr.io) can still be quite helpful for libraries.
5 Replies
Iunno about automating release but publishing can be automated with CI
Publishing packages - Docs - JSR
Learn how to publish packages to JSR.
I personally do this:
https://github.com/retraigo/fortuna/blob/main/.github/workflows/publish.yml
I know how to publish. I am interested in automating the release process (which can be done with sematic-release in node).
- Increase version in deno.json (depending on commit messages)
- Create tag
- Create release
GitHub
GitHub - semantic-release/semantic-release: :package::rocket: Fully...
:package::rocket: Fully automated version management and package publishing - semantic-release/semantic-release
@NeTT Interesting reaction. May I ask for your opinion on this? 😀