fix: fail release cuts on unavailable tag evidence - #394
Merged
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: liatrio/autogov/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
A fresh API-mode release cut now stops when remote tags cannot be observed, before local file changes or mutating API requests. It preserves the wrapped API error; a successfully observed empty tag list still permits a cut. Resume and local/auto-mode behavior are unchanged.
Trusted-root diagnostics move to stderr without changing selection/fallback. Untagged ghrel policy references warn with the resolved latest tag. Ineffective commit-author/email flags remain accepted with deprecation warnings, exported option fields remain for compatibility, and a dead internal branch-tip helper is removed. README documents the existing pre-1.0 major-bump rule and the legacy VSA metric formula without changing either contract.
Validation: full task verify (lint and race tests,75.4% coverage), task build, focused package tests and CLI compatibility check pass; five existing optional tests skip. A regression first reproduced the API-error defect and now proves failure before file/API mutations, alongside existing-tag and successful-empty-list controls. Independent review found no actionable issues. The added fixture uses native new(expression) for compatibility with SDK migration #388.
AI-assisted implementation and independent tooling review; human review remains required.
Closes #393