Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: revert "feat: upload-client funcs have options.piece to opt in to piece link calculation (#1220) #1224

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

vasco-santos
Copy link
Contributor

This reverts commit c38000e.

Needs #1223 merged.

Alternatively, we can keep the code as is and make the default true. However, I feel that our current way of making computation in the client and not do Bucket events would go against supporting this as optional

@vasco-santos vasco-santos changed the title Revert "feat: upload-client funcs have options.piece to opt in to piece link calculation (#1220) fix: revert "feat: upload-client funcs have options.piece to opt in to piece link calculation (#1220) Dec 7, 2023
@vasco-santos vasco-santos merged commit 2f238bf into main Dec 7, 2023
3 of 4 checks passed
@vasco-santos vasco-santos deleted the fix/revert-piece-calculation-optional branch December 7, 2023 10:02
vasco-santos pushed a commit that referenced this pull request Dec 7, 2023
🤖 I have created a release *beep* *boop*
---


##
[12.3.1](upload-client-v12.3.0...upload-client-v12.3.1)
(2023-12-07)


### Fixes

* revert "feat: upload-client funcs have options.piece to opt in to
piece link calculation
([#1220](#1220))
([#1224](#1224))
([2f238bf](2f238bf))
* upgrade fr32-sha2-256-trunc-254-padded-binary-tree-multihash to 3.1.1.
([#1223](#1223))
([0801d90](0801d90))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants