alvarolorentedev
commented
3 years ago @chmac sorry for the really late response. somehow i miss the notification of this issue.
You are correct I am doing an automatic release every week. The main intention is update dependencies to remove probable vulnerabilities. I did this before there where services that automate this, so I might move to one of them at some point.
When I run this process I validate compatibility and quality by running the unit and integration tests before the commit of updates takes place.
This automatic updates follow semver as it does not affect interface or functionality. When a change on the library causes one of those a minor or major version will be released.
Hoper this answers your question.
Sorry again for the late response 🙏
It looks like there's a new version of this package published every week, with either no changes at all, or from time to time a dependency version bump. I'm guessing it's a fully automated process. Is it supposed to be publishing every week?
Are you following semver? Is it safe to publish a new patch release after running
yarn upgrade? I imagine that this might cause major version bumps in the dependencies, which in turn could introduce breaking changes. But I might be missing something.Also, thanks for this package, looks like it'll be a great way to start automating my new drone!