Skip to content

Commit

Permalink
chore(main): release 2.6.0 (#257)
Browse files Browse the repository at this point in the history
🤖 I have created a release *beep* *boop*
---


## [2.6.0](v2.5.0...v2.6.0)
(2024-08-02)


### Features

* parse all the response items from MeijuCloud for get_device_inf
([#231](#231))
([1976eb6](1976eb6))


### Bug Fixes

* **cli:** authenticate to get keys
([#256](#256))
([a017e7a](a017e7a))
* tank is always seen as full
([#255](#255))
([3524405](3524405))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
  • Loading branch information
rokam authored Aug 5, 2024
1 parent a017e7a commit 8e58d38
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 1 deletion.
13 changes: 13 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,18 @@
# Changelog

## [2.6.0](https://github.com/rokam/midea-local/compare/v2.5.0...v2.6.0) (2024-08-02)


### Features

* parse all the response items from MeijuCloud for get_device_inf ([#231](https://github.com/rokam/midea-local/issues/231)) ([1976eb6](https://github.com/rokam/midea-local/commit/1976eb63578698d2b9a745a92c9c61a887219e0d))


### Bug Fixes

* **cli:** authenticate to get keys ([#256](https://github.com/rokam/midea-local/issues/256)) ([a017e7a](https://github.com/rokam/midea-local/commit/a017e7af46130266226f6c9a100b05703dd6cb5c))
* tank is always seen as full ([#255](https://github.com/rokam/midea-local/issues/255)) ([3524405](https://github.com/rokam/midea-local/commit/3524405fd36131deb83c9ded236eb686860f58c2))

## [2.5.0](https://github.com/rokam/midea-local/compare/v2.4.0...v2.5.0) (2024-07-30)


Expand Down
2 changes: 1 addition & 1 deletion midealocal/version.py
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
"""Midea Local Version."""

__version__ = "2.5.0"
__version__ = "2.6.0"

0 comments on commit 8e58d38

Please sign in to comment.