v0.6.0
Changed
- Gateway URL
--gateway-urlis no longer defaulting to predefined URL. User has to provide it via CLI orGATEWAY_URLenvironment 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:8080to ensure no confusion withlocalhost:8080subdomain gateway feature in IPFS implementations like Kubo.
- Subdomain URL and UX related to subdomain tests
- The
--subdomain-urlis no longer set by default. - User has to provide the origin of the subdomain gateway via CLI or
SUBDOMAIN_GATEWAY_URLto be used during subdomain tests. This aims to ensure no confusion about which domain name is being tested. - Simplified the way
--subdomain-urlworks. We no longer run implicit tests againsthttp://localhostin addition to the URL passed via--subdomain-url. To test more than one domain, run test multiple times. localhostsubdomain gateway tests are no longer implicit. To run tests againstlocalhostuse--subdomain-url http://localhost:8080
- The
- DNSLink test fixtures changed
- DNSLink fixtures no longer depend on
--subdomain-urland use unrelated*.example.orgdomains instead. gateway-conformance extract-fixturescreatesdnslinks.IPFS_NS_MAPwith content that can be directly set asIPNS_NS_MAPenvironment variable supported by various implementations, incl. Kubo and Rainbow.
- DNSLink fixtures no longer depend on
- Docker: image can now be run under non-root user
- HTTP Proxy tests are no longer implicit. An explicit spec named
proxy-gatewayexists now, and can be disabled via--specs -proxy-gateway.
This release was brought to you by the Shipyard team.
