Guarddog v3 announcement#742
Merged
Merged
Conversation
christophetd
approved these changes
May 26, 2026
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
2 participants
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
self.github.tag-release.v3dd-octo-sts policyWhat changes
tag-release.yml— triggers on[main, v3]; octo-sts policy is nowself.github.tag-release.${{ github.ref_name }};:latestDocker tag is only pushed when running frommaindocker-publish.yml(manual failsafe path) —:latestonly forv2.*tagspr.yml— runs checks on PRs intomainorv3What doesn't change
Main's existing release flow: pushes to main still trigger
tag-release, still publish:latest, still use the.mainpolicy. No artifacts are published by this PR.