v1.1.0

What's Changed

• Load the STAC root and each collection lazily by @mrshll in #35
• Sync outside-comment notification workflow by @aldenks in #38
• Rename CLAUDE.md to AGENTS.md (CLAUDE.md symlinked) by @mrshll-agent in #42
• Recognize CF geographic coordinates in the catalog integration test by @aldenks in #46

Behaviour changes

The catalog is now loaded lazily: the root once, and each dataset's collection only when you use that dataset.

• list() is a single request. It reads dataset ids from the catalog root and no longer fetches every collection. That makes it faster, but it no longer confirms each dataset is reachable. It also lists every dataset in the catalog, including any this version of the client can't open.
• One bad dataset no longer breaks the others. A collection is fetched and parsed the first time you call open(), get_store() or get_repository() for it, then cached. If a collection can't be fetched or read by this client version, only that dataset errors. Failures aren't cached, so the next call retries.
• Errors about an unsupported storage scheme or credential type now suggest upgrading dynamical-catalog.
• Custom catalogs must use the standard layout. If you set DYNAMICAL_STAC_CATALOG_URL, the catalog must link each collection from the root as a child at <root>/<id>/collection.json. Dataset ids come from those URLs. A catalog with another layout fails to load, and a collection whose id doesn't match its URL raises InvalidCatalogError when you open it. stac.dynamical.org and stac-staging.dynamical.org already use this layout, so the default setup needs no changes.

New Contributors

• @mrshll-agent made their first contribution in #42

Full Changelog: v1.0.1...v1.1.0