fix: bump package number to ensure w3up-client depends on >= access@15 #836
Conversation
This file contains 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
I released these packages in the wrong order, so the new w3up-client still depends on v14, which points at access.web3.storage. tweak the version dep (in a way I'll revert later) to ensure we move past that.
|
merging without approval because this is a mechanical hack that I'll be reverting after I release the package |
travis
pushed a commit
that referenced
this pull request
Jul 21, 2023
🤖 I have created a release *beep* *boop* --- ## [8.0.1](w3up-client-v8.0.0...w3up-client-v8.0.1) (2023-07-21) ### Bug Fixes * bump package number to ensure w3up-client depends on >= access@15 ([#836](#836)) ([b095b7c](b095b7c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
I released these packages in the wrong order, so the new w3up-client still depends on v14, which points at access.web3.storage. tweak the version dep (in a way I'll revert later) to ensure we move past that.