gifify version is out of date in public registry image

[kirbysayshi]

If you run:

$ docker run -it --rm -v $(pwd):/data maxogden/gifify --version
...
2.1.1

Whereas gifify in npm is currently at 2.1.5 (and has a fix I'd like). The public registry image is of course prebuilt. I could clone this repo and build it myself, but I wonder if there's a better way to keep gifify up to date without too much effort from you? I honestly don't know, and have been running into a similar issue when using docker for builds / tools.

One way I found is to do a COPY /package.json / within the Dockerfile, and then as long as the version is pinned it will rebuild with proper caching. But that doesn't help this case too much, because this is a public tool.

Anyway, thanks for this great image! It's been extremely useful!

[whitfin]

You can set the entrypoint to be npm i -g gifify && gifify and I think it'd update every time you start a container