bump fabric-chaincode-go

[pfi79]

#5086

[denyeart]

Having a Draft PR open to prepare the change is fine by me, but let's wait for fabric-chaincode-go to get completely settled and released before we bump the version in core fabric.

[denyeart]

This looks good... let's see if github makes us rebase given my recent update to go.mod.

[denyeart]

Not a huge deal but we usually don't like to have multiple commits in a PR that supersede each other. I usually do git commit --amend to keep a clean commit history. More details at https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html#updating-a-pull-request

[pfi79]

This looks good... let's see if github makes us rebase given my recent update to go.mod.

I didn't wait, I made a rebase.

[pfi79]

Not a huge deal but we usually don't like to have multiple commits in a PR that supersede each other. I usually do git commit --amend to keep a clean commit history. More details at https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html#updating-a-pull-request

I can close, redo and open a new pr.

[denyeart]

Sorry I broke your PR :-)
I just prefer to do incremental dependency updates in case something breaks...

[pfi79]

Sorry I broke your PR :-) I just prefer to do incremental dependency updates in case something breaks...

No, no, don't be sorry. You did the right thing. I don't like big changes myself.