feat: add upload/shard/list capability and implementation#680
Merged
feat: add upload/shard/list capability and implementation#680
upload/shard/list capability and implementation#680Conversation
Contributor
Website preview 🔗✨ |
Peeja
approved these changes
Feb 26, 2026
packages/capabilities/src/types.ts
Outdated
Comment on lines
+979
to
+980
| export interface UploadShardListSuccess | ||
| extends Omit<ListResponse<UnknownLink>, 'before' | 'after'> {} |
Member
There was a problem hiding this comment.
question (non-blocking): Why does this one not have a before and after? Just not worth implementing the bi-directional pagination? Maybe we should have a separate generic type that isn't bi-directional, and then make a bi-directional one by adding before and after to it, just for clarity when reading the code. Or maybe that's not worth it.
Member
Author
There was a problem hiding this comment.
Yeah it's just complexity I wasn't sure if we wanted for shard listing. We can add it later if needs be. I will add the separate type as suggested.
Member
|
Oh! You'll want to add a release plan, too. |
alanshaw
added a commit
to storacha/w3infra
that referenced
this pull request
Mar 4, 2026
Changes to the upload table implementation to allow shards to be listed for a given upload. refs storacha/upload-service#680
This was referenced Mar 4, 2026
alanshaw
pushed a commit
that referenced
this pull request
Mar 4, 2026
…9.99, @storacha/ui-core@2.4.162, @storacha/filecoin-client@1.0.19, @storacha/access@1.6.8, @storacha/upload-client@1.4.0, @storacha/capabilities@2.3.0, @storacha/filecoin-api@2.1.4, @storacha/client@2.1.0, @storacha/blob-index@1.2.8, @storacha/upload-api@3.2.0, @storacha/router@1.1.5, @storacha/cli@2.1.0 (#683) ## @storacha/encrypt-upload-client@1.1.79 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/upload-client to 1.4.0 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/client to 2.1.0 ## @storacha/ui-react@2.9.99 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/encrypt-upload-client to 1.1.79 - Updated @storacha/ui-core to 2.4.162 ## @storacha/ui-core@2.4.162 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/access to 1.6.8 - Updated @storacha/client to 2.1.0 ## @storacha/filecoin-client@1.0.19 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/capabilities to 2.3.0 ## @storacha/access@1.6.8 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/capabilities to 2.3.0 ## @storacha/upload-client@1.4.0 (2026-03-04) ### 🚀 Features - feat: add `upload/shard/list` capability and implementation ([#680](#680)) ### 🧱 Updated Dependencies - Updated @storacha/filecoin-client to 1.0.19 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/blob-index to 1.2.8 ### ❤️ Thank You - ash ## @storacha/capabilities@2.3.0 (2026-03-04) ### 🚀 Features - feat: add `upload/shard/list` capability and implementation ([#680](#680)) ### ❤️ Thank You - ash ## @storacha/filecoin-api@2.1.4 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/filecoin-client to 1.0.19 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/router to 1.1.5 ## @storacha/client@2.1.0 (2026-03-04) ### 🚀 Features - feat: add `upload/shard/list` capability and implementation ([#680](#680)) ### 🧱 Updated Dependencies - Updated @storacha/filecoin-client to 1.0.19 - Updated @storacha/access to 1.6.8 - Updated @storacha/upload-client to 1.4.0 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/blob-index to 1.2.8 - Updated @storacha/upload-api to 3.2.0 ### ❤️ Thank You - ash ## @storacha/blob-index@1.2.8 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/capabilities to 2.3.0 ## @storacha/upload-api@3.2.0 (2026-03-04) ### 🚀 Features - feat: add `upload/shard/list` capability and implementation ([#680](#680)) ### 🧱 Updated Dependencies - Updated @storacha/access to 1.6.8 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/filecoin-api to 2.1.4 - Updated @storacha/blob-index to 1.2.8 - Updated @storacha/router to 1.1.5 ### ❤️ Thank You - ash ## @storacha/router@1.1.5 (2026-03-04) ### 🧱 Updated Dependencies - Updated @storacha/capabilities to 2.3.0 ## @storacha/cli@2.1.0 (2026-03-04) ### 🚀 Features - feat: add `upload/shard/list` capability and implementation ([#680](#680)) ### 🧱 Updated Dependencies - Updated @storacha/access to 1.6.8 - Updated @storacha/capabilities to 2.3.0 - Updated @storacha/client to 2.1.0 - Updated @storacha/upload-api to 3.2.0 ### ❤️ Thank You - ash Co-authored-by: Rachabot <rachabot@storacha.network>
alanshaw
pushed a commit
that referenced
this pull request
Mar 4, 2026
🤖 I have created a release *beep* *boop* --- ## [3.0.0](console-v2.20.2...console-v3.0.0) (2026-03-04) ### ⚠ BREAKING CHANGES * Return values for `upload/add`, `upload/list` and `upload/get` no longer include a `shards` field that contains the CIDs of the shards of the upload. You must now call `upload/shard/list` to obtain shards for an upload. This is not technically a breaking change because the field was optional. However, any API consumer relying on the field to contain the shard listing for a given upload will no longer show shards for a given upload. ### Features * add `upload/shard/list` capability and implementation ([#680](#680)) ([63bf146](63bf146)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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
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.
Adds a capability for (paginated) listing of shards for an upload.
When an upload is VERY large, it will be split into many shards. We have made changes to support this when invoking
upload/add, but when invokingupload/listit is easy to exceed the max response size (~6MB) since all shard CIDs are returned for every upload.This PR alters the
upload/listresponse so that it NEVER returns shard CIDs. Instead, to obtain shard CIDs for a given upload you must invokeupload/shard/list, passing the upload root CID.BREAKING CHANGE: Return values for
upload/add,upload/listandupload/getno longer include ashardsfield that contains the CIDs of the shards of the upload. You must now callupload/shard/listto obtain shards for an upload. This is not technically a breaking change because the field was optional. However, any API consumer relying on the field to contain the shard listing for a given upload will no longer show shards for a given upload.