We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
w3console
NB: if you are logged in via the nft.storage console domain, you can only use nft.storage as a provider (same with web3.storage)
The text was updated successfully, but these errors were encountered:
chore(main): release react-keyring 5.1.0 (storacha#487)
3f63cdf
🤖 I have created a release *beep* *boop* --- ## [5.1.0](storacha/w3ui@react-keyring-v5.0.0...react-keyring-v5.1.0) (2023-03-30) ### Features * use new faster auth function ([storacha#483](storacha/w3ui#483)) ([372f249](storacha/w3ui@372f249)) --- 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: Travis Vachon <[email protected]>
279d1b1
🤖 I have created a release *beep* *boop* --- ## [5.1.0](storacha/w3ui@react-keyring-v5.0.0...react-keyring-v5.1.0) (2023-03-30) ### Features * use new faster auth function ([storacha#483](storacha/w3ui#483)) ([f100ec2](storacha/w3ui@f100ec2)) --- 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: Travis Vachon <[email protected]>
No branches or pull requests
w3console
NB: if you are logged in via the nft.storage console domain, you can only use nft.storage as a provider (same with web3.storage)
The text was updated successfully, but these errors were encountered: