chore: release 0.9.0 - #170
Open
tobiasdiez wants to merge 1 commit into
Open
Conversation
10 tasks
tobiasdiez
force-pushed
the
release-please--branches--main
branch
from
July 21, 2026 06:53
11bf8e4 to
f3d7660
Compare
tobiasdiez
added a commit
that referenced
this pull request
Jul 22, 2026
## Purpose of this PR The release PR #170 resets the version to 0.1.0 as this is the default for release-please. With this change here, release-please should correctly realize that the last released version is 0.8.1. (In the future, release-please will update the manifest automatically, so this here is a one-time action.) Moreover, configure release-please so that it doesn't include the branch name in the PR title, and finally also update the uv.lock file (which release-please doesn't do automatically googleapis/release-please#2561). ## Type of change (Make sure to delete from the Type-of-change list the items not relevant to your PR) - [ ] Bug fix - [ ] Refactoring - [ ] New feature - [ ] Minor change - [ ] Major change ## Checklist: - [ ] I have updated the in-code documentation of all changed classes and functions - [ ] I have added in-code documentation and type hints to all new classes and functions - [ ] I have adapted the howtos - [ ] I have adapted the examples - [ ] If this change should entail a version update, I have bumped the version in the `pyproject.toml` file accordingly
tobiasdiez
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
July 22, 2026 12:05
554bb5d to
67dd21d
Compare
5 tasks
tobiasdiez
added a commit
that referenced
this pull request
Jul 27, 2026
## Purpose of this PR The tests in the release PR #170 are still failing since the uv file was not updated, due to a stupid mistake on my side (forgot to replace `my-package` by `flodym`). Should be fixed now. ## Checklist: - [x] I have used the [Conventional Commits](https://www.conventionalcommits.org/) format for my PR title (and commit messages) - [ ] I have updated the in-code documentation of all changed classes and functions - [ ] I have added in-code documentation and type hints to all new classes and functions - [ ] I have adapted the howtos - [ ] I have adapted the examples
tobiasdiez
force-pushed
the
release-please--branches--main
branch
5 times, most recently
from
July 27, 2026 19:24
6a6ed85 to
bfbf5d2
Compare
tobiasdiez
force-pushed
the
release-please--branches--main
branch
from
July 29, 2026 07:32
bfbf5d2 to
cb15fb9
Compare
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
1 participant
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.9.0 (2026-07-29)
🔖 Features
🐛 Bug Fixes
Dimension.from_npto support pandas string arrays (#160) (351c33d)📚 Documentation
example1, fix typos, add links to API (#178) (c3bb0c9)🧹 Miscellaneous
uv.lockfile after version increment (#175) (832e39d)This PR was generated with Release Please. See documentation.