Repository navigation
Tags
Tags
release linux binaries and packages from a tag push Releases were cut by hand: tag, then goreleaser from a workstation, which is also where the minisign key and the quay.io credentials live. Nothing happened when a tag was pushed. Adds a Release workflow that runs the tests and then goreleaser on any v* tag, publishing the four linux binaries plus the deb and rpm packages to the GitHub release with the same asset names as before. .goreleaser.linux.yml is a separate config on purpose: it drops the darwin and windows builds, the minisign signatures (the key is on a locally mounted path) and the quay.io images (they need buildx and a registry login), so the full .goreleaser.yml stays the workstation path for those. Its release mode is append, so a hand run for the same tag adds the signatures and the remaining platforms to the release the workflow created.
Filtering out server host at client side to prevent testing through l… …ocal network stack (#25) * applying a filter to prevent hosts from testing against themselfs. * using slices.Clone * changing pointers to cloning * Fixing host cloning and filtering * Adding proper cli return code on error * updating vuln check * Fixing nil reference
PreviousNext