Repository navigation
fix(updates): accept fork revision releases on the update page - #11
Merged
Merged
Conversation
The update page validated release metadata against the upstream repository URL and plain X.Y.Z versions, so this fork's X.Y.Z-revised.N releases from Alumos/SubLane failed client validation and showed a request error. Accept the fork's stable version format and release URL, and treat revision builds as stable builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The update page rejected Alumos/SubLane release URLs and X.Y.Z-revised.N versions during client-side validation, showing "could not confirm the update request status". Verified against the live GitHub API with a local 0.19.2-revised.8 build.
🤖 Generated with Claude Code