search

ipfs / rainbow

A specialized IPFS HTTP gateway
https://docs.ipfs.tech/reference/http/gateway/
Other
66 stars 11 forks source link

chore(deps): bump ipfs/gateway-conformance from 0.5.1 to 0.6.0 #147

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps ipfs/gateway-conformance from 0.5.1 to 0.6.0.

Release notes

Sourced from ipfs/gateway-conformance's releases.

v0.6.0

Changed

  • Gateway URL
    • --gateway-url is no longer defaulting to predefined URL. User has to provide it via CLI or GATEWAY_URL environment variable or the test suite will refuse to start.
    • This aims to ensure no confusion about which gateway endpoint is being tested.
    • Docs and examples use --gateway-url http://127.0.0.1:8080 to ensure no confusion with localhost:8080 subdomain gateway feature in IPFS implementations like Kubo.
  • Subdomain URL and UX related to subdomain tests
    • The --subdomain-url is no longer set by default.
    • User has to provide the origin of the subdomain gateway via CLI or SUBDOMAIN_GATEWAY_URL to be used during subdomain tests. This aims to ensure no confusion about which domain name is being tested.
    • Simplified the way --subdomain-url works. We no longer run implicit tests against http://localhost in addition to the URL passed via --subdomain-url. To test more than one domain, run test multiple times.
    • localhost subdomain gateway tests are no longer implicit. To run tests against localhost use --subdomain-url http://localhost:8080
  • DNSLink test fixtures changed
    • DNSLink fixtures no longer depend on --subdomain-url and use unrelated *.example.org domains instead.
    • gateway-conformance extract-fixtures creates dnslinks.IPFS_NS_MAP with content that can be directly set as IPNS_NS_MAP environment variable supported by various implementations, incl. Kubo and Rainbow.
  • Docker: image can now be run under non-root user
  • HTTP Proxy tests are no longer implicit. An explicit spec named proxy-gateway exists now, and can be disabled via --specs -proxy-gateway.

v0.5.2

Changed

  • Fixed: relaxed dag-cbor error check (#205)
  • Fixed: Header().Has works properly for checking multiple values (#207)
Changelog

Sourced from ipfs/gateway-conformance's changelog.

[0.6.0] - 2024-06-10

Changed

  • Gateway URL
    • --gateway-url is no longer defaulting to predefined URL. User has to provide it via CLI or GATEWAY_URL environment variable or the test suite will refuse to start.
    • This aims to ensure no confusion about which gateway endpoint is being tested.
    • Docs and examples use --gateway-url http://127.0.0.1:8080 to ensure no confusion with localhost:8080 subdomain gateway feature in IPFS implementations like Kubo.
  • Subdomain URL and UX related to subdomain tests
    • The --subdomain-url is no longer set by default.
    • User has to provide the origin of the subdomain gateway via CLI or SUBDOMAIN_GATEWAY_URL to be used during subdomain tests. This aims to ensure no confusion about which domain name is being tested.
    • Simplified the way --subdomain-url works. We no longer run implicit tests against http://localhost in addition to the URL passed via --subdomain-url. To test more than one domain, run test multiple times.
    • localhost subdomain gateway tests are no longer implicit. To run tests against localhost use --subdomain-url http://localhost:8080
  • DNSLink test fixtures changed
    • DNSLink fixtures no longer depend on --subdomain-url and use unrelated *.example.org domains instead.
    • gateway-conformance extract-fixtures creates dnslinks.IPFS_NS_MAP with content that can be directly set as IPNS_NS_MAP environment variable supported by various implementations, incl. Kubo and Rainbow.
  • Docker: image can now be run under non-root user
  • HTTP Proxy tests are no longer implicit. An explicit spec named proxy-gateway exists now, and can be disabled via --specs -proxy-gateway.

[0.5.2] - 2024-05-20

Changed

  • Fixed: relaxed dag-cbor error check (#205)
  • Fixed: Header().Has works properly for checking multiple values (#207)
Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 month ago

Looks like ipfs/gateway-conformance is up-to-date now, so this is no longer needed.