@flyboarder simply adding a shutdown hook doesn't seem to cut it, I assume (given the namespace in which add-shutdown-hook! resides) that I'll have to perhaps make a pod ?

And in more general terms, if anyone has an example of making a new pod with shutdown hooks (and what the hell that actually even implies), I'd be grateful

@pseud checkout the boot-nodejs serve task, uses shutdown hooks to kill rogue nodejs threads

⚠️ boot-semver now supports Continuous Deployment v1.5.0 ⚠️ https://github.com/degree9/boot-semver

@flyboarder awesome that you can push snapshots like this, but is it pushing on every file change?

in that case yes!

I dont recommend it, but the goal was to solve the repeated use of the version task in pipelines

there is now an internal atom used to track the version

Is it possible to do it ? A conditional watch it is not possible but you could maybe read meta from the version file

Ah yeah no

The push task needs to do that

yep, pom and push have been patched and replaced

via replace-task!

they also track the new atom

Got it yeah

I guess it would be a great addition

im not sure it is, I think the correct way to store mutative data is in the env map

Uhm in any case I like the idea of auto pushing