chore(chaincode): bump cc-tools to v1.0.3 - #1
Merged
Merged
Conversation
Update github.com/hyperledger-labs/cc-tools from v1.0.0 to v1.0.3 (latest release) in the chaincode module. Cumulative changes across v1.0.1..v1.0.3: - v1.0.1: @lastTxID asset metadata - v1.0.2: PurgePrivateData on MockStub - v1.0.3: force @assetType presence on NewKey/Key generation No main.go changes are required: goshare's chaincode entrypoint matches the reference cc-tools-demo (identical except module import paths), and none of these releases alter the chaincode startup API. Build passes and the chaincode unit smoke test (SetupCC + MockInit StartupCheck) passes under v1.0.3. Co-Authored-By: Claude <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
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.
Summary
Updates
github.com/hyperledger-labs/cc-toolsfrom v1.0.0 → v1.0.3 (latest release) in thechaincodemodule. Isolated change — onlychaincode/go.modandchaincode/go.sum.What changed upstream (v1.0.1 → v1.0.3)
@lastTxIDmetadata (the tx that last changed the state)PurgePrivateDataadded toMockStub@assetTypepresence onNewKey/ Key generationmain.goNo changes required. goshare's
chaincode/main.gomatches the referencehyperledger-labs/cc-tools-demo(identical except module import paths), and none of these releases alter the chaincode startup API. The CCaaS server-mode entrypoint is unchanged.Verification
go build ./...— OKgo test github.com/hyperledger-labs/goshare/chaincode, the CI-gating test) — passes;TestMainrunsSetupCC()+MockInit, exercisingassets.StartupCheck()/tx.StartupCheck()under v1.0.3.Note on the integration suite (
./tests)The godog/Docker integration suite (currently commented out in CI) does not pass in the local sandbox, but the failure is unrelated to this bump: the chaincode was not committed to the test channel during network bring-up (peer discovery: "Chaincode goshare isn't defined in channel mainchannel"), and a pre-existing ccapi error-handling bug (
invalid WriteHeader code 11→ gin panic) turns that into an empty HTTP 200. Neither depends on the cc-tools version (ccapihas no cc-tools dependency).