fix: image and log banner say riptide-collector, not riptide#53
Merged
Conversation
The first release.yaml run pushed to ghcr.io/trick77/riptide because the
workflow used \${{ github.repository }}. The image, Python package, module,
and historic ci.yaml path all carry the name 'riptide-collector', not
'riptide' — the GitHub repo is the odd one out.
Pin the image name explicitly to riptide-collector and align the startup
log banner with the same name so Splunk panels grepping
msg=\"<service> version: …\" match the image tag readers actually pull.
The stray 0.1.0 git tag and the orphan ghcr.io/trick77/riptide package
are deleted out-of-band; the next release run starts fresh at 0.1.0
under the correct path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan