chore: release main

[ds-release-bot]

🤖 I have created a release beep boop

0.3.0-beta.2

0.3.0-beta.2 (2026-02-19)

Features

• feat: Add AbortSignal support to GeoTIFF.fetchTile (9d133b8)

geotiff: 0.3.0-beta.2

0.3.0-beta.2 (2026-02-19)

Features

• feat: Add AbortSignal support to GeoTIFF.fetchTile (9d133b8)

---

This PR was generated with Release Please. See documentation.

[kylebarron]

@gadomski seems weird that it automatically bumps from 0.3.0-beta.1 to 0.4.0-beta.1? I'd prefer it publish a new beta and then at some point we publish all of 0.2.0 to 0.3.0 at once.

[gadomski]

Yeah I agree, I think there's a way to tweak the config to not have it do that. I'll take a look later today or tomorrow morning?

[kylebarron]

Yeah no rush!

[gadomski]

I tweaked the PR description of #243 and re-ran to fix the version.

I did a bit more reading, and I think release-please is pretty poor at pre-release stuff ... most of the docs I found recommended using a dedicated branch with a different pre-release config to cut betas. So if alphas/betas/rcs are pretty regular part of your workflow, either

1. Use Release-as: x.y.z-beta.n in the PR descriptions, or
2. Abandon release-please as Too Much Work™

[kylebarron]

dedicated branch with a different pre-release config to cut betas

!!!

That sounds so annoying

So if alphas/betas/rcs are pretty regular part of your workflow, either

I use them pretty frequently to essentially do integration testing between my projects to validate they're all working together before publishing the standard release.

The problem is when I forget to make a mainline release 🙈

ahem

[ds-release-bot]

🤖 Created releases:

• v0.3.0-beta.2
• geotiff-v0.3.0-beta.2

🌻