🤖 I have created a release *beep* *boop*
---


##
[14.1.0](w3up-client-v14.0.0...w3up-client-v14.1.0)
(2024-06-04)


### Features

* add blob/get
([#1484](#1484))
([328039d](328039d))

---
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>
Co-authored-by: Vasco Santos <[email protected]>

From @vasco-santos:
1. if we already have a http/put receipt, we should not send one
2. if we already receive in next a blob accept receipt, we should not
await on the receipt generation

🤖 I have created a release *beep* *boop*
---


##
[16.1.1](upload-client-v16.1.0...upload-client-v16.1.1)
(2024-06-05)


### Fixes

* reuse http/put and blob/accept receipts when available
([#1495](#1495))
([416802e](416802e))

---
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>

🤖 I have created a release *beep* *boop*
---


##
[14.1.1](w3up-client-v14.1.0...w3up-client-v14.1.1)
(2024-06-05)


### Fixes

* trigger w3up client release with new client
([#1497](#1497))
([9616f0d](9616f0d))

---
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 hasn't been working for a long time now and I don't think we even
use the docs it generates.

No need to write to this bucket anymore - both freeway and hoverboard
use content claims.

This PR updates the `index/add` handler to publish an [index
claim](https://github.com/w3s-project/content-claims?tab=readme-ov-file#index-claim)
for the added index.

Reading an index from the index claim allows freeway and hoverboard to
serve blocks from all of the shards without having to request a location
claim for each block.

refs storacha/blob-fetcher#10

This forces callers to decode `Uint8Arrays` that may come from user
input before the storage method is called and that means we don't just
use them without validation that they are actually a multihash.

BREAKING CHANGE: `AllocationsStorage` and `BlobsStorage` methods not
take `MultihashDigest` types instead of `Uint8Array`s.

🤖 I have created a release *beep* *boop*
---


##
[18.0.0](upload-api-v17.1.0...upload-api-v18.0.0)
(2024-06-07)


### ⚠ BREAKING CHANGES

* `AllocationsStorage` and `BlobsStorage` methods not take
`MultihashDigest` types instead of `Uint8Array`s.

### Features

* publish index claim
([#1487](#1487))
([237b0c6](237b0c6))


### Fixes

* stop writing to DUDEWHERE
([#1500](#1500))
([cf0a1d6](cf0a1d6))
* use MultihashDigest type in stores
([#1474](#1474))
([6c6a3bd](6c6a3bd))

---
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>