-
Notifications
You must be signed in to change notification settings - Fork 120
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
Ideas for automation of release process #109
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I don't have much experience with javascript tools, but in other languages that use similar constructs, I found it most helpful to have the developer update package-lock.json and commit it as usual, but then have a CI component that performs some basic checks that ensure that the package-lock.json is compatible with the package.json. I'm not sure how to do this with |
Validating the lockfile using a continuous integration step sounds like a good plan to me 👍 |
grocy
version tag is used consistently (i.e. inMakefile
,docker-compose
,package.json
, ...)package.json
andpackage-lock.json
files (and the associated container release version references in them) (Reduce the number of files in which the GROCY_IMAGE_TAG value has to be updated during version upgrades #170)Makefile
version reference improvementsdocker-compose.yml
version reference improvementsRebuild(outdated due to file removal in Reduce the number of files in which the GROCY_IMAGE_TAG value has to be updated during version upgrades #170)package-lock.json
automatically?Tag the(currently a WONTDO)latest
image on Docker Hub?It may be possible to perform some of these checks by using
git
pre-commit / pre-push scripts.The text was updated successfully, but these errors were encountered: