This release hardens the plugin release pipeline: goreleaser no longer double-runs on a published release, and the datumctl plugin catalog now updates itself automatically.
What's new
- Fixed goreleaser running twice per release — publishing a release through the GitHub UI fired both
push: tagsandrelease: published, causing two goreleaser processes to race uploading the same assets; the plugin-publishing job is now gated on the release event so it runs exactly once. (#66) - Automatic
datumctlplugin catalog updates — after a release, a new job mints a short-lived GitHub App token and opens a PR againstmilo-os/cli-pluginsbumpingplugins/ipam.yamlwith the released version, per-platform URLs, and checksums, replacing the manual manifest edit after each release. (#66)
Note
No API type changes. Existing clients and resources keep working without any update.