Skip to content

chore(main): release 3.5.0 - #67

Merged
roquerodrigo merged 1 commit into
mainfrom
release-please--branches--main--components--ha-ttlock-ble
Aug 7, 2026
Merged

chore(main): release 3.5.0#67
roquerodrigo merged 1 commit into
mainfrom
release-please--branches--main--components--ha-ttlock-ble

Conversation

@roquerodrigo

@roquerodrigo roquerodrigo commented Aug 7, 2026

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

3.5.0 (2026-08-07)

Features

  • options: make the reconnect cooldown configurable and add a permanent connection mode (d5182a3)

Bug Fixes

  • keep the lock state when the operation-log read fails (566f2ab), closes #74
  • remove registry devices for locks that leave the entry's key set (2e43dea)

Code Refactoring

  • drop dead API surface and hoist record-type sets to module level (c430338)

Dependencies

  • bump homeassistant to 2026.8.0 with its matching test harness (e69a570)

Documentation

  • align README, CODE_STYLE and CLAUDE.md with the actual codebase (af29a08)

Continuous Integration

  • run checks on pull requests targeting any branch (73bea78)
  • run code scanning on pull requests targeting any branch (20e0d71)

Miscellaneous Chores

  • repair scripts/setup and align local tooling with the uv workflow (a984db9)
  • sync uv.lock with the 3.4.0 release (79b5f07)

This PR was generated with Release Please. See documentation.

@roquerodrigo
roquerodrigo force-pushed the release-please--branches--main--components--ha-ttlock-ble branch 2 times, most recently from 4170095 to 0fa2aa4 Compare August 7, 2026 17:02
@roquerodrigo
roquerodrigo force-pushed the release-please--branches--main--components--ha-ttlock-ble branch from 0fa2aa4 to 9acd79a Compare August 7, 2026 18:53
@roquerodrigo
roquerodrigo merged commit 4eabbfd into main Aug 7, 2026
9 checks passed
@roquerodrigo

Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A failed operation-log read discards an already-successful state read, so the lock entity never refreshes

1 participant