chore: release 0.2.1#28
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 82a82d556d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [project] | ||
| name = "ferrolabsai" | ||
| version = "0.2.0" | ||
| version = "0.2.1" |
There was a problem hiding this comment.
This release bump leaves ferrolabsai/_version.py falling back to "0.2.0". In environments that import the SDK from a source checkout or vendored copy without installed package metadata, importlib.metadata.version("ferrolabsai") raises PackageNotFoundError, so ferrolabsai.__version__ and the client User-Agent still report 0.2.0 even though the project metadata is 0.2.1. Please update the fallback value as part of the release bump.
Useful? React with 👍 / 👎.
Cut the 0.2.1 release: - Date the changelog section (2026-06-13). - Bump pyproject.toml to 0.2.1 so a `v0.2.1` tag passes the publish job's tag/version assertion. - Bump the _version.py fallback to 0.2.1 so __version__ and the client User-Agent report 0.2.1 in source/vendored checkouts without installed package metadata (importlib.metadata.PackageNotFoundError path).
82a82d5 to
81bba3a
Compare
1 participant
Summary
Cut the 0.2.1 release.
CHANGELOG.md: promote the[Unreleased]section to## [0.2.1] — 2026-06-13.pyproject.toml: bumpversion0.2.0→0.2.1so av0.2.1tag passes the publish job's tag/version assertion.Contents of 0.2.1 (already merged into
mainvia #26):FerroStreamErroron malformed SSE chunks instead of silently dropping them (sync + async).admin.dashboard()andadmin.plugins.list()(all three response shapes); streaming malformed-chunk regression tests.Why a PR (not an amend)
mainis a protected branch, so the already-merged release commit can't be amended/force-pushed. This lands the version bump the normal way.Release steps after merge
main.git tag v0.2.1 && git push origin v0.2.1..github/release.yml).