This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.6.1 instead.
Reason given by maintainers: -
openccu-loom-types — retired
The generated Pydantic models and enum catalogue that this package used to
publish now ship inside
openccu-loom-client, as
openccu_loom_client.wire.
# before
from openccu_loom_types.rest import DeviceSummary
from openccu_loom_types.enums import Interface
# now
from openccu_loom_client.wire.rest import DeviceSummary
from openccu_loom_client.wire.enums import Interface
Nothing about the wire contract changed. The modules are byte-for-byte the same generated output, from the same daemon assets, by the same generators — they just live in the package that consumes them.
What to do
Nothing, if you depend on openccu-loom-client: it carries the bindings itself
and no longer requires this distribution.
If openccu-loom-types is still installed in an environment — Home Assistant
never uninstalls an abandoned requirement, so this is the common case —
upgrading to 0.6.0 removes the stale modules and pulls in the client that
holds the real ones. 0.6.0 ships no Python modules at all; it is metadata
and a dependency.
Leaving the old version installed is harmless rather than dangerous: the two
distributions own disjoint top-level packages, so an orphaned
openccu_loom_types is inert. Upgrading is cleanup, not a fix.
Why
The split cost a release of its own for every daemon release. Since the
auto-tag landed on 2026-06-22, 154 daemon releases produced 84 releases here,
84 of 84 out of a feat: regenerate from openccu-loom … commit — not one
carried a hand-written line — while 54 of 106 publications never reached a pin
in any consumer. No consumer ever imported the package directly.
A daemon release now opens a regeneration pull request in the client and stops there: no version bump, no auto-merge, no tag.
This repository
Kept for its history and so the distribution name stays owned. The modules,
the generators (script/gen/), the regeneration workflow and the
reproducibility guard all live in the client repository now.
1 maintainer
Release files for openccu-loom-types 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openccu_loom_types-0.6.0.tar.gz | 3.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openccu_loom_types-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / openccu_loom_types-0.6.0.tar.gz
| Download URL | openccu_loom_types-0.6.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04b29cc8b9c873d8d1d3ef22ef630225f2baac22ad6b4f48fdd05ff278c99e0a
|
|
BLAKE2b-256 checksum How to use checksums |
5aa828c9b358edd4ba931a7245a6f9b2ef4557dd3cdf55e77028bc4019831198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency logRelease files / openccu_loom_types-0.6.0-py3-none-any.whl
| Download URL | openccu_loom_types-0.6.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8857e9259ef287ddd8821491fafa189832d312cec857d4954689564da78b1d85
|
|
BLAKE2b-256 checksum How to use checksums |
acee3aff257bcf31b8f8b835ce386ead94ca14588f7766d52a7d1fbc1759f547
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.
Transparency log
