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

Automated publishing after NPM bump update #142

Open
davidhorak opened this issue May 18, 2021 · 0 comments
Open

Automated publishing after NPM bump update #142

davidhorak opened this issue May 18, 2021 · 0 comments
Assignees
Labels
c-rfc Request for comments on an idea or problem. w-later No priority but aligns with product vision.

Comments

@davidhorak
Copy link
Contributor

davidhorak commented May 18, 2021

Description

Currently, consumers of this library only benefit from the dependency updates when we release a new version manually. To improve that, we may add automated npm publish / GH release triggered by NPM dump.

This should represent a minor package update therefore it could released without any change log.

Some Options

  • Triggered once a month, via a scheduled workflow.
  • Triggered on merge to master when changes detected in the package-lock.json compared to previous commit.

Note: This would apply to any Briza's open-source library, i.e. currently: https://github.com/briza-insurance/illogical

@davidhorak davidhorak added c-rfc Request for comments on an idea or problem. w-later No priority but aligns with product vision. labels May 18, 2021
@davidhorak davidhorak mentioned this issue May 18, 2021
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c-rfc Request for comments on an idea or problem. w-later No priority but aligns with product vision.
Projects
None yet
Development

No branches or pull requests

2 participants