Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(#155): use semantic release npm module #162

Merged
merged 1 commit into from
Oct 14, 2024
Merged

fix(#155): use semantic release npm module #162

merged 1 commit into from
Oct 14, 2024

Conversation

andrablaj
Copy link
Member

Description

(hopefully) closes #155

Per this conversation, the npm module is responsible for editing the package.json, and is needed in the configuration.

Additional resources on the topic.

Code review checklist

  • Readable: Concise, well named, follows the style guide, documented if necessary.
  • Documented: Configuration and user documentation on cht-docs
  • Tested: Unit and/or e2e where appropriate
  • Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

@andrablaj andrablaj requested a review from njuguna-n October 14, 2024 12:05
@andrablaj andrablaj merged commit 09ed265 into main Oct 14, 2024
6 checks passed
@andrablaj andrablaj deleted the 155-release branch October 14, 2024 13:41
@medic-ci
Copy link

🎉 This PR is included in version 1.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump up the version in package.json after release
3 participants