Skip to content

Commit

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


##
[4.2.0](access-api-v4.1.0...access-api-v4.2.0)
(2022-12-15)


### Features

* **access-api:** access-api version endpoint has publicKey property
([#317](#317))
([474d561](474d561))

---
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
hugomrdias authored Dec 16, 2022
1 parent 474d561 commit 4d4a44a
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,6 +1,6 @@
{
"packages/access-client": "9.2.0",
"packages/access-api": "4.1.0",
"packages/access-api": "4.2.0",
"packages/capabilities": "2.1.0",
"packages/upload-client": "5.2.0"
}
7 changes: 7 additions & 0 deletions packages/access-api/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [4.2.0](https://github.com/web3-storage/w3protocol/compare/access-api-v4.1.0...access-api-v4.2.0) (2022-12-15)


### Features

* **access-api:** access-api version endpoint has publicKey property ([#317](https://github.com/web3-storage/w3protocol/issues/317)) ([474d561](https://github.com/web3-storage/w3protocol/commit/474d561845f7c10a785421ef95e552385861a970))

## [4.1.0](https://github.com/web3-storage/w3protocol/compare/access-api-v4.0.0...access-api-v4.1.0) (2022-12-14)


Expand Down
2 changes: 1 addition & 1 deletion packages/access-api/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@web3-storage/access-api",
"version": "4.1.0",
"version": "4.2.0",
"description": "Access API",
"type": "module",
"main": "dist/worker.js",
Expand Down

0 comments on commit 4d4a44a

Please sign in to comment.