Repository navigation
chore(main): release 0.1.0 - #16
Merged
kristoflemmens merged 1 commit intoOct 25, 2026
Merged
kristoflemmens merged 1 commit into
kristoflemmens merged 1 commit into
Conversation
klconsultancy-release-bot
Bot
requested a review
from kristoflemmens
as a code owner
October 24, 2026 15:03
klconsultancy-release-bot
Bot
force-pushed
the
release-please--branches--main--components--thermia-genesis
branch
18 times, most recently
from
October 25, 2026 13:17
3950770 to
c6f9c38
Compare
2 of 4 tasks
kristoflemmens
added a commit
that referenced
this pull request
Oct 25, 2026
## What and why Refs #15 CI fails on the release PR #16: release-please bumps `pyproject.toml` to 0.1.0 but leaves `uv.lock` at 0.0.0, and `uv sync --locked` then refuses the lockfile. This would happen on every release. This adds an `extra-files` entry to `release-please-config.json`, so release-please also bumps the `thermia-genesis` package version in `uv.lock`. It uses the TOML updater with `$.package[?(@.name.value=='thermia-genesis')].version`; release-please's TOML parser wraps values, hence `.value`. **Verification:** this can't be run locally. After the merge, the release workflow rewrites #16, which must then also change `uv.lock` (`version = "0.0.0"` → `"0.1.0"` for `thermia-genesis`), and its CI must turn green. **Also, in the same release preparation:** release-please could not parse the squash commit of #26 (`feat: add the ThermiaGenesis API…`). A wrapped body line starting with `addresses:` read as a footer, so the changelog left out the public API. #26 now has a `BEGIN_COMMIT_OVERRIDE` block in its description, and #16 lists it after a re-run. ## Checklist - [ ] The test was written first and failed for the right reason before the implementation (n/a: release configuration) - [x] Coverage stays at 100% - [ ] `docs/design.md` / `CONTEXT.md` updated if a design choice or domain term changed (n/a) - [x] PR title follows Conventional Commits (`feat:`, `fix:`, `docs:`, ...) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
klconsultancy-release-bot
Bot
force-pushed
the
release-please--branches--main--components--thermia-genesis
branch
from
October 25, 2026 13:39
c6f9c38 to
e501d83
Compare
kristoflemmens
deleted the
release-please--branches--main--components--thermia-genesis
branch
October 25, 2026 13:40
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.1.0 (2026-10-25)
Features
Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.