Version Packages - #108
Merged
Merged
Version Packages#108
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@1001-digital/layers.evm@4.0.0
Major Changes
d2baa8bThanks @jwahdatehagh! - Remove the defaultevm.ipfsGateway. It pointed athttps://ipfs.io/ipfs/,which no longer works in a browser: ipfs.io answers browser-shaped requests
with a Cloudflare managed challenge whose interstitial carries
X-Frame-Options: SAMEORIGIN, so IPFS embeds fail with "refused to connect"and uncached images never load. Every widely-used public gateway behaves the
same way, so there is no default worth shipping.
Apps that resolve IPFS content must now set
evm.ipfsGatewayin theirapp.config, pointing at a gateway they operate or have an arrangement with.Left unset, resolution falls through to
dweb-fetch's own ipfs.io default andwill not load in a browser; the layer logs a warning in development.