Bump the vendor/UnifiSharp pointer to v0.3.0 - #431
Merged
Conversation
The engine consumes Chrison.UnifiSharp 0.3.0 from nuget.org, while the vendored source still pinned the commit before 0.2.0 — so anyone reading vendor/UnifiSharp saw a client two releases behind the one actually being built against, with no sign of it. Picks up the API-key auth + rest/user work (#17) and static DNS on the v2 site API (#18). The auto-bump bot only advances stacks/*, so vendor pointers are a manual step. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
the
dependencies
4 tasks
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.
The engine consumes
Chrison.UnifiSharp0.3.0 from nuget.org, whilevendor/UnifiSharpstill pinned the commit before 0.2.0. So anyone reading the vendored source saw a client two releases behind the one actually being built against, with nothing indicating the gap.Picks up:
rest/user, port-forward update (v0.2.0)v0.3.0)Pointer only — no engine change, and the build already resolves 0.3.0 from the package feed either way.
Worth noting for next time: the auto-bump bot only advances
stacks/*, sovendor/*pointers drift silently and indefinitely.vendor/ProxmoxSharpandvendor/SynoSharpmay be in the same state; I haven't checked them here.🤖 Generated with Claude Code