Remove obsolete repository release flow - #1097
Merged
Merged
Conversation
The central distribution repository now owns changelog generation, maintenance pull requests, tagging, release creation, and artifact publication. Keeping RoboRev's tag-triggered publisher would start a second release path for the same tag. The scheduled and manual asset verifier remains available. Local GoReleaser snapshot validation also remains unchanged. Generated with Codex Co-authored-by: Codex <noreply@openai.com>
roborev: Combined Review (
|
Release publication moved out of this repository, but the asset verifier must still check each release as soon as it becomes public. Trigger it from the published release event and use that event's exact tag. Scheduled verification and manual tag selection remain unchanged. Generated with Codex Co-authored-by: Codex <noreply@openai.com>
roborev: Combined Review (
|
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.
RoboRev releases are now orchestrated by the central distribution repository. This removes the old local changelog, maintenance, and tag scripts, along with the tag-triggered publisher, so one tag cannot start a second release path.
The existing asset verifier still runs automatically when a GitHub Release is published. It also remains available on its daily schedule and through manual dispatch.
.goreleaser.yamlandmake release-snapshot-checkremain for local, non-publishing package validation.