Skip to content

Commit 60ff933

Browse files
authored
Merge pull request #13 from ctrondlp/P2-release-0.6.0
chore: release 0.6.0 -- bump the four version sites and log the badge…
2 parents 8187ce9 + 8b765eb commit 60ff933

5 files changed

Lines changed: 39 additions & 5 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 35 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ All notable changes to python-libei are recorded here. The format follows
55
[semantic versioning](https://semver.org/spec/v2.0.0.html) — with the usual
66
0.x caveat that the API may still change between minor versions.
77

8-
## [Unreleased]
8+
## [0.6.0] - 2026-09-22
99

1010
### Added
1111

@@ -53,6 +53,28 @@ All notable changes to python-libei are recorded here. The format follows
5353
connection and lifecycle events, which have no getter and are read through
5454
`event_type`.
5555

56+
- **CI, PyPI and license badges on the README.** The three things a reader
57+
checks before installing anything -- whether the suite is green on `main`,
58+
what the current release is, and under what license -- each took a click
59+
through to somewhere else. The PyPI badge is also the one version statement
60+
in the repository that reads what is actually *published*: the prose lines
61+
that `tests/test_documentation_shape.py` guards are held to this checkout's
62+
`libei.__version__`, which says nothing about what `pip install` would
63+
fetch.
64+
65+
- **`.coderabbit.yaml`**, turning the Docstring Coverage pre-merge check off
66+
and telling the reviewer not to ask for docstrings under `tests/`. That
67+
check scores a whole diff against a single percentage threshold and its
68+
schema offers no per-path option, so it cannot see that
69+
`[tool.ruff.lint.per-file-ignores]` ignores `D100`-`D104` and `D107` under
70+
`tests/*` deliberately -- matching both sibling repos, on the grounds that
71+
each test is named for the behaviour it pins -- and so it objected on every
72+
PR that adds tests, which is most of them. Coverage of `src/` is untouched:
73+
ruff's pydocstyle rules enforce it in `scripts/pre-commit-test.sh`, and
74+
those *are* path-aware. The same exclusion is repeated as a
75+
`path_instructions` entry, which is where it can be path-scoped, so it
76+
holds whether or not the check is ever switched back on.
77+
5678
### Changed
5779

5880
- **The docstring-completeness check now runs everywhere, and covers
@@ -88,6 +110,18 @@ All notable changes to python-libei are recorded here. The format follows
88110
covered -- that `CreateSession` carries a `session_handle_token`, whose
89111
absence crashes xdg-desktop-portal 1.22.1 outright.
90112

113+
- **39 docstrings on the dunders and private helpers that had none.** No check
114+
asked for them: ruff's pydocstyle rules treat an underscore-prefixed name as
115+
non-public, and this repo's config ignores `D105` outright -- so `__init__`,
116+
`__eq__`, `__hash__`, `__repr__`, `__del__`, `__enter__`/`__exit__`,
117+
`__init_subclass__`, `_cobject.CObject._get_or_create()`,
118+
`LazyLibrary._ensure_loaded()` and both `_log_callback`s went undocumented
119+
while being the definitions whose behaviour is least guessable from the
120+
signature: pointer adoption and the per-hierarchy identity cache, a failed
121+
`dlopen` cached rather than retried, a C function resolved on first call
122+
rather than at bind time. `help()` and an IDE's hover show all of them, and
123+
neither cares that a name starts with an underscore.
124+
91125
### Fixed
92126

93127
- **The README's link to the developer pages landed on a file listing.**

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ and why, is in
129129

130130
## Status
131131

132-
Beta (`0.5.2`), published on [PyPI](https://pypi.org/project/python-libei/)
132+
Beta (`0.6.0`), published on [PyPI](https://pypi.org/project/python-libei/)
133133
since `0.1.0`, and **the API is not frozen** — expect renames before 1.0.
134134

135135
The injection path is exercised end to end against the real libraries by the

‎docs/developers/verification.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# What has actually been verified
22

3-
The package is beta (`0.5.2`) and the API is not frozen — expect renames
3+
The package is beta (`0.6.0`) and the API is not frozen — expect renames
44
before 1.0. This page is what that qualifier covers, concretely: which paths
55
have been driven against real libraries, which have only ever been driven
66
against fakes, and which libei versions the whole thing has met.

‎pyproject.toml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
44

55
[project]
66
name = "python-libei"
7-
version = "0.5.2"
7+
version = "0.6.0"
88
description = "Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis"
99
readme = "README.md"
1010
license = "MIT"

‎src/libei/__init__.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,6 @@
3131
Beta: the API is not frozen.
3232
"""
3333

34-
__version__ = "0.5.2"
34+
__version__ = "0.6.0"
3535

3636
__all__ = ["__version__"]

0 commit comments

Comments
 (0)