chore(main): release 0.3.0-beta.1

[ds-release-bot]

🤖 I have created a release beep boop

0.3.0-beta.1 (2026-02-18)

Features

• affine: Create new affine standalone package as port of Python affine (ce7b73d)
• Create morecantile subpackage (#238) (20b3ace)
• Create new geotiff subpackage, abstracting over @cogeotiff/core (#223) (4fa5230)
• geotiff: generate TileMatrixSet from GeoTIFF instance (#235) (cb1106e)
• geotiff: High-level CRS handling from GeoTIFF GeoKeys (#236) (559dc03)
• geotiff: Overhaul GeoTIFF and Overview classes (#225) (857a8c2)
• geotiff: Support decoding JPEG and WebP-compressed COGs (#229) (3dc6281)
• Initial GeoTIFF dynamic decoder API (#226) (5d611f3)
• Overhaul to use our geotiff package & generic TileMatrixSet support (#208) (860a701), closes #216

Bug Fixes

• Fix shader caching (#221) (2a02439)

Miscellaneous Chores

• release 0.3.0-beta.1 (#239) (8ba364e)

---

This PR was generated with Release Please. See documentation.

[kylebarron]

@gadomski these PRs are auto-created for every PR merged to main..?

[gadomski]

@gadomski these PRs are auto-created for every PR merged to main..?

If the pr is named fix or feat. It skips chore and other ones. It'll auto-update this PR as you accumulate changes. If you want to modify how release-please sees a PR post-facto, you can https://github.com/googleapis/release-please?tab=readme-ov-file#how-can-i-fix-release-notes.

[kylebarron]

@gadomski do you know how I publish a beta?

[gadomski]

You can use an empty commit:

git commit --allow-empty -m "chore: release 2.0.0-beta.0" -m "Release-As: 2.0.0-beta.0"

Or you could edit a PR description of an included PR to include a a commit message override:

BEGIN_COMMIT_OVERRIDE
feat: awesome thing

Release-As: 2.0.0-beta.0
END_COMMIT_OVERRIDE

You'd then need to re-run the release-please workflow.

[kylebarron]

Interesting, thanks. Since I can't push to main I think I have to make a PR with that PR description

[gadomski]

Interesting, thanks. Since I can't push to main I think I have to make a PR with that PR description

I think you can edit an existing PR (e.g. #224) and then just re-run the workflow?

[kylebarron]

Wait you can edit a PR description, not the merged commit message, and it'll pick that up?

[kylebarron]

Interesting, thanks. Since I can't push to main I think I have to make a PR with that PR description

re-run the workflow?

re-run what workflow?

[gadomski]

Wait you can edit a PR description, not the merged commit message, and it'll pick that up?

Yup: https://github.com/googleapis/release-please?tab=readme-ov-file#how-can-i-fix-release-notes