Prepare Release 0.1.2 (And Release Helper) by posborne · Pull Request #110 · fastly/compute-sdk-python

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne · 2026-06-02T22:37:26Z

Release bump; so I don't forget the steps I added a helper with a Make target for doing the bumps a little bit easier. Mostly just wanted to be a bit more competent in getting all the uv.lock updates for the examples as they exist currently.

The docs were also updated to reference this and added the pre-release -> release step to get things on to PyPI.

This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Using the fancy helper.

erikrose

Could you remove the lookbehind? Then we're ready to rock.

erikrose · 2026-06-03T13:43:22Z

-5. (Pending) If the release is built successfully, it will make its way to PyPI
- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on


erikrose · 2026-06-03T13:43:38Z

- via trusted publishing.
-
+5. If the release workflow succeeds, a new pre-release will be avilable on
+ Github. Afer review and update of the generated changelog, use the


erikrose · 2026-06-03T14:03:28Z

+ cargo_path = root_dir / "crates" / "fastly-compute-py" / "Cargo.toml"
+
+ # pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]
+ update_file_version(pyproject_path, r'(?<=^version = ")[^"]+', new_version)


I imagine (though didn't measure) that the lookbehind is less efficient than doing this…
# pyrpoject.toml: Matches `version = "X.Y.Z"` under [project]update_file_version(pyproject_path, r'^version = "[^"]+', 'version = "'+new_version) # Cargo.toml: Matches `version = "X.Y.Z"` under [package]update_file_version(cargo_path, r'^version = "[^"]+', 'version = "'+new_version)
…since it has to find every instance of a run of non-quote chars and then look behind it to see if it's preceded by "version = ". The forward-looking version shouldn't do any unnecessary work.
Okay, I couldn't help myself. I measured. Before:
100,000 iterations in 2.436s — 24.358 µs/iter
After:
100,000 iterations in 0.013s — 0.134 µs/iter
:-)

I can remove the lookbehind; N here (the size of the file) will never be large enough for it to matter at all and this is a utility running on a controlled input run in a context that is not performance sensitive in the least.

True, it's just that it hurts my soul. :-)

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

posborne added 3 commits June 2, 2026 17:31

release: Add helper for bumping version, update CONTRIBUTING.md
2945978
This is not necessary but bumping the example uv.lock files felt a bit annoying, so I decided to script it. The pre-release -> release instructions in our notes were also missing, so I added that in.

Fix spurious local lint failures
1991f28
If the examples dependencies haven't been already pulled in by another command, lint can fail. Run our ruff checks with those extra bits in the environment explicitly.

Bump version to 0.1.2
f1e8e9d
Using the fancy helper.

posborne requested a review from erikrose June 2, 2026 22:37

erikrose approved these changes Jun 3, 2026
View reviewed changes

posborne added 2 commits June 3, 2026 11:32

Use simpler regex for version replacement
790104a

CONTRIBUTING.md typo corrections
d40ba49

posborne merged commit 891eb32 into mainJun 3, 2026
1 check passed

posborne deleted the posborne/rel-0.1.2 branch June 3, 2026 16:36

Uh oh!

Conversation

posborne commented Jun 2, 2026

Uh oh!

erikrose left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

posborne commented Jun 2, 2026

Uh oh!

erikrose left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

posborne commented Jun 2, 2026

Uh oh!

erikrose left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation