Repository navigation
After 2.0.0: main back into develop, update-hop pin names 2.0.0 - #523
Merged
Merged
Conversation
Release 2.0.0 (source 7bc3704, package run 41375420248)
The seed serves 2.0.0 on stable since 2 Nov. CI's update journey installed the old rc.1 pin by Undo from a stable Home and the channel guard refused it.
…rge commit release-publish.sh checked_tag refuses a tag that does not name the source commit; v2.0.0 was placed on 7bc3704 that way.
This was referenced Nov 3, 2026
Open
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
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.
After stable 2.0.0 (#93):
Source review: GO on 1ee873a, 3a2991b, 2533cc1.