[kylebarron]

Note

This PR was written by Claude (Claude Code), not by @kylebarron.

Bumps version to 0.10.0-beta.1 in the root package.json and in every packages/*/package.json, ready for the first 0.10 beta. The publish workflow sees beta in the version and publishes to npm under the beta dist-tag, so latest stays on 0.9.0.

CHANGELOG.md gets a v0.10.0-beta.1 section listing the 19 PRs merged since v0.9.0.

Publish @developmentseed/range-reader by hand before tagging

@developmentseed/range-reader (#806) isn't on npm yet, and @developmentseed/geotiff and @developmentseed/deck.gl-geotiff depend on it. The publish workflow can't create it: it publishes only through trusted publishing (OIDC), and npm can add a trusted publisher only to a package that already exists. Pushing the tag first would fail at range-reader. pnpm publish --recursive stops at the first failure, so packages published before it in the run would be out, and the rest, including geotiff and deck.gl-geotiff, would not.

Once this is merged, from an up-to-date main:

1. Publish it once, as a public package under the beta tag. Its prepublishOnly script builds it first.

   cd packages/range-reader
   pnpm publish --tag beta --access public --no-git-checks

2. Give it the same trusted publisher as the other packages (workflow release.yml, environment release), in its settings on npmjs.com or with:

   npm trust github @developmentseed/range-reader --file release.yml --repo developmentseed/deck.gl-raster --env release --allow-publish

3. Tag the merge commit v0.10.0-beta.1 and push the tag. The workflow skips range-reader, since that version is already on npm, and publishes the other ten packages.

Breaking changes

• feat(deck.gl-geotiff)!: open COGs with COGSource #799: COGLayer takes a single source: an opened COGSource, or any input of COGSource.open. geotiff becomes source, onGeoTIFFLoad becomes onSourceLoad, and epsgResolver and concurrencyLimiter move to COGSource.open.
• feat(deck.gl-geotiff)!: open the files of one scene with MultiCOGSource #801: MultiCOGLayer does the same with MultiCOGSource. sources: { red: { url } } becomes source: { red: url }, MultiCOGSourceConfig is removed, and files that don't share a CRS and an extent are rejected.
• feat(deck.gl-geotiff)!: take MosaicLayer's items as data, and pass their sources as source #804: MosaicLayer's sources becomes deck.gl's data, and MosaicSource becomes MosaicItem. The callbacks get the item's opened source as source, and onViewportLoad's entries are { item, source }.
• fix(deck.gl-geotiff)!: stop passing renderSource an abort signal #821: renderSource gets only { source }, without signal.
• feat(deck.gl-zarr)!: open GeoZarr data with ZarrSource #812: ZarrLayer takes a ZarrSource, or a zarrita group or array, as source. node, variable, metadata and epsgResolver are removed (metadata becomes ZarrSource.open's geoZarrMetadata), and the type parameters are now ZarrLayer<DataT, Dtype, Store>.
• feat(geotiff)!: read COGs through the range reader #807: GeoTIFF.fromUrl no longer takes chunkSize or cacheSize. They're RangeReader options now (minMetadataReadBytes, cache.metadataBytes).

Two behavior changes aren't marked breaking:

• feat(deck.gl-geotiff): coalesce COG tile reads by default #809: COG tile reads are coalesced by default, and COGLayer and MultiCOGLayer default to maxRequests: 256 and debounceTime: 50.
• feat: fetch tiles again when updateTriggers.getTileData or ZarrLayer's selection changes #818: changing updateTriggers.getTileData, or ZarrLayer's selection, fetches tiles again, and the old tiles are removed at once.

🤖 Written by Claude Code