I have mentioned this before, but without any answers or follow ups. Any reason for not publishing and updating the npm package?
I have mentioned this before, but without any answers or follow ups. Any reason for not publishing and updating the npm package?
The original creator/maintainer stopped working on the repository and doing the releases. Is this something you’d have time and interest in taking over?
Hey, @Jardar - That’s a great question, and @kevin is right. It hasn’t been updated because the community needs someone to work on updating it. If you’d like to help out, we have a guide for how you can contribute to our GitHub: How to Contribute Code to Liquibase | Liquibase.org
Thanks,
Tabby
Hi,
sorry the hear that. I do not have the necessary knowledge about lb/npm to take on this task. With regards to package deploy I was kind of expecting this to be part of some CI/CD deployment routine?