5 Commits

Include renames

Author	SHA1	Message	Date
ReactorcoremeltdownandClaude Opus 5.5	d314188247	Deploy when versions.mk changes ... The deploy pipeline watched a VERSION file that does not exist, so a version bump built the image but never deployed it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-11-02 12:30:28 +01:00
Reactorcoremeltdown	0af5ecc5a7	Allowing manual push	2026-10-30 13:09:22 +01:00
Reactorcoremeltdown	d40fc67722	Trigger deploy on editing Golang	2026-10-30 13:04:43 +01:00
root	3a499532f3	Make the deploy stamp the version and fire on Go changes ... Two things in the deploy did not do what they looked like: build-server passed --build-arg APP_VERSION, but the Dockerfile declares ARG VERSION. An unknown build arg is ignored with a warning, so every deployed image was stamped "dev": `keeporgd -version` and the image's version label both said so, whatever the tag claimed. The build pipeline's path filter listed 'VERSION', a file this repository does not have, and '*.go', which under doublestar matches only top-level Go files, of which there are none. So a push that changed only Go code or only the version did not trigger a build. Now versions.mk and '**/*.go'. Proved: built with --build-arg VERSION=0.5.0 and ran -version in the container, which now reports 0.5.0.	2026-10-30 10:49:46 +01:00
Reactorcoremeltdown	da503eac2a	Initial deploy	2026-10-30 10:01:11 +01:00