Describe what should be investigated or refactored
We should do a tag-based release workflow for the zarf-injector as well so that it is easier to correlate the source code of a given zarf-injector binary back to it's source code. This could work very similarly to the existing release workflow.
We would like to be able to build a custom regex handler in a tool like renovate in our own init packages to pick up changes in the zarf injector if/when that happens.
Describe what should be investigated or refactored
We should do a tag-based release workflow for the zarf-injector as well so that it is easier to correlate the source code of a given
zarf-injector
binary back to it's source code. This could work very similarly to the existingrelease
workflow.Links to any relevant code
https://github.com/defenseunicorns/zarf/blob/main/.github/workflows/release.yml https://github.com/defenseunicorns/zarf/blob/main/.github/workflows/build-rust-injector.yml
Additional context
Add any other context or screenshots about the technical debt here.