Repository navigation
fix(release): resolve consumer subpackage dependencies - #17
Merged
Merged
Conversation
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.
Summary
Install the
convention,forward, andmanagedpackages at the exact release tag before building the clean consumer. This resolves their dependencies and writes the required consumergo.sumentries.Why
The 0.6.0 release passed proxy visibility and source SHA checks, but consumer compilation failed with a missing
github.com/coder/websocketchecksum. The verification script fetched only the module root before creating a program that imports the SDK subpackages.Failure: https://github.com/QoderAI/qoder-cloud-agents-sdk-go/actions/runs/38568900835/attempts/2
Verification
bash -n.v0.6.0package.go.sumerror.go build.Impact
Only the release verification workflow changes. SDK source, API behavior, dependencies, documentation, and changelog are unchanged; live integration tests are not required. No credentials or generated test output are included.
After merge, resume by dispatching the updated main workflow with version
0.6.0, source SHA1d7f987d83261036aa1f61074956ba04e512660a, and batch IDsdk-0.6.0-20261014-01. Reuse the existing tag; rerunning the old workflow would retain the faulty verification command.