Release v0.12.0 #8743
Merged
Release v0.12.0 #8743
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
Not that they will ever happen in the current implementation, but it makes the linter happy and covers our back for future.
This fixes some tests which expect "refs local" and "repo gc" outputs to match the CIDs produced when adding data. These operations are now outputting CIDv1-raw hashes, regardless of the original CIDs used to address those blocks, so some tests fail. The fix is usually: * To use "block stat" to check if a block was correctly gc'ed * To convert the CIDs to multihash (using cid-fmt) and compare those instead
This sharness test provides 2 datastore blocks directly. One of them (corresponding to an "insecure block") is not a CIDv0 therefore it needs to be migrated and stored with its raw-multihash ID. The (raw) CID of the block used in the test remains the same. The other block needs no changes.
Compare multihashes rather than CIDs.
tar.gz got mangled because of reasons known to github, this does the correct upload every time by forcing github to interpret payload as an opaque stream of bytes without anything fancy
* only copy files from dist.ipfs.io which have associated checksum files (also copy the checksum files) * verify checksums before copying * also, ignore path from sha512sum output, which sometimes has absolute path on dist.ipfs.io website Co-authored-by: Marcin Rataj <[email protected]>
feat: switch to raw multihashes for blocks
* chore: [email protected] https://github.com/ipfs/js-ipfs/blob/master/packages/ipfs/CHANGELOG.md#0610-2021-12-15 * chore: [email protected] (cherry picked from commit 14046d0)
This is to make it easier to understand why the multifetcher is falling back to a different fetcher. (cherry picked from commit 4f3eb4c)
* feat: refactor Fetcher interface used for downloading migrations * feat: add RetryFetcher for migration downloads * feat: 3 retries for each HTTP migration download (cherry picked from commit b1ffc87)
hacdias
pushed a commit
to ipfs/boxo
that referenced
this pull request
Jan 27, 2023
Release v0.12.0 This commit was moved from ipfs/kubo@06191df
gammazero
pushed a commit
to ipfs/boxo
that referenced
this pull request
Sep 28, 2023
Release v0.12.0 This commit was moved from ipfs/kubo@06191df
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.
No description provided.