Skip to content

chore: release v0.1.5 #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vtz merged 1 commit into from
May 25, 2026
Merged

chore: release v0.1.5 #20

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/).

<!-- towncrier release notes start -->

## [0.1.5](https://github.com/vtz/opensomeip-python/releases/tag/v0.1.5) - 2026-05-24

### Features

- Update opensomeip C++ submodule to **v0.1.0**. Adapt pybind11 bindings to
upstream API changes:
- SD: `ServiceInstance.minor_version` widened to 32-bit, `EventGroupSubscription`
gains `major_version`, `offer_service` accepts `eventgroup_ids`.
- Events: expose `EventPublisher.set_default_client_endpoint`,
`EventSubscriber.set_default_endpoint` and `set_endpoint_resolver`.
- Transport: expose TCP Magic Cookie config and static helpers.
(Closes #21)

### Bug Fixes

- Operations that require the native C++ extension (RPC calls, transport send,
event subscriptions) now raise clear errors (`RpcError`, `TransportError`,
`RuntimeError`) instead of silently returning empty/fake responses or dropping
messages when the extension is unavailable. (Fixes #17)

### Documentation

- Add "Verify native extension" subsection to the README after Installation.
- Update the Troubleshooting section to describe the new error-raising behavior.

### Miscellaneous

- Add `.hypothesis/` and `uv.lock` to `.gitignore`.

## [0.1.4](https://github.com/vtz/opensomeip-python/releases/tag/v0.1.4) - 2026-04-18

### Features
Expand Down
4 changes: 2 additions & 2 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "scikit_build_core.build"

[project]
name = "opensomeip"
version = "0.1.4"
version = "0.1.5"
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Runtime __version__ is out of sync with package version.

pyproject.toml is bumped to 0.1.5, but src/opensomeip/_version.py:1 still reports __version__ = "0.1.4" and is re-exported by src/opensomeip/__init__.py:3. Users will observe conflicting versions.

Proposed fix 
--- a/src/opensomeip/_version.py
+++ b/src/opensomeip/_version.py
@@
-__version__ = "0.1.4"
+__version__ = "0.1.5"
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pyproject.toml` at line 7, Update the runtime __version__ constant to match
the package version in pyproject.toml: change the value of __version__ in
src/opensomeip/_version.py to "0.1.5" (this value is re-exported by
src/opensomeip/__init__.py), so the module-level __version__ symbol and the
package metadata stay in sync.

description = "Python bindings for the opensomeip C++ SOME/IP stack"
readme = "README.md"
license = "Apache-2.0"
Expand Down Expand Up @@ -58,7 +58,7 @@ wheel.packages = ["src/opensomeip"]
cmake.build-type = "Release"

[tool.scikit-build.cmake.define]
OPENSOMEIP_PYTHON_VERSION = "0.1.4"
OPENSOMEIP_PYTHON_VERSION = "0.1.5"

[tool.pytest.ini_options]
testpaths = ["tests"]
Expand Down
Loading