Skip to content

Commit

Permalink
chore(main): release access 16.5.1 (#1090)
Browse files Browse the repository at this point in the history
🤖 I have created a release *beep* *boop*
---


##
[16.5.1](access-v16.5.0...access-v16.5.1)
(2023-11-08)


### Bug Fixes

* fix export paths for JS files
([#1089](#1089))
([1a5d1aa](1a5d1aa))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
  • Loading branch information
it-dag-house authored Nov 8, 2023
1 parent 1a5d1aa commit cb46ee9
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"packages/access-client": "16.5.0",
"packages/access-client": "16.5.1",
"packages/filecoin-api": "4.0.6",
"packages/filecoin-client": "3.0.1",
"packages/capabilities": "11.2.0",
Expand Down
7 changes: 7 additions & 0 deletions packages/access-client/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [16.5.1](https://github.com/web3-storage/w3up/compare/access-v16.5.0...access-v16.5.1) (2023-11-08)


### Bug Fixes

* fix export paths for JS files ([#1089](https://github.com/web3-storage/w3up/issues/1089)) ([1a5d1aa](https://github.com/web3-storage/w3up/commit/1a5d1aa1b1bfdb188cb69712a74404b89d8200af))

## [16.5.0](https://github.com/web3-storage/w3up/compare/access-v16.4.0...access-v16.5.0) (2023-11-07)


Expand Down
2 changes: 1 addition & 1 deletion packages/access-client/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@web3-storage/access",
"version": "16.5.0",
"version": "16.5.1",
"description": "w3access client",
"homepage": "https://github.com/web3-storage/w3-protocol/tree/main/packages/access-client",
"repository": {
Expand Down

0 comments on commit cb46ee9

Please sign in to comment.