mirror of
https://github.com/python-kasa/python-kasa.git
synced 2024-12-22 19:23:34 +00:00
0647adaba0
This major brings major changes to the library by adding support for devices that require authentication for communications, all of this being possible thanks to the great work by @sdb9696! This release adds support to a large range of previously unsupported devices, including: * Newer kasa-branded devices, including Matter-enabled devices like KP125M * Newer hardware/firmware versions on some models, like EP25, that suddenly changed the used protocol * Tapo-branded devices like plugs (P110), light bulbs (KL530), LED strips (L900, L920), and wall switches (KS205, KS225) * UK variant of HS110, which was the first device using the new protocol If your device that is not currently listed as supported is working, please consider contributing a test fixture file. Special thanks goes to @SimonWilkinson who created the initial PR for the new communication protocol!
58 lines
1.5 KiB
Markdown
58 lines
1.5 KiB
Markdown
1. Set release information
|
|
|
|
```bash
|
|
# export PREVIOUS_RELEASE=$(git describe --abbrev=0)
|
|
export PREVIOUS_RELEASE=0.3.5 # generate the full changelog since last pyhs100 release
|
|
export NEW_RELEASE=0.4.0.dev4
|
|
```
|
|
|
|
2. Update the version number
|
|
|
|
```bash
|
|
poetry version $NEW_RELEASE
|
|
```
|
|
|
|
3. Write a short and understandable summary for the release.
|
|
|
|
* Create a new issue and label it with release-summary
|
|
* Create $NEW_RELEASE milestone in github, and assign the issue to that
|
|
* Close the issue
|
|
|
|
3. Generate changelog
|
|
|
|
```bash
|
|
# gem install github_changelog_generator --pre
|
|
# https://github.com/github-changelog-generator/github-changelog-generator#github-token
|
|
export CHANGELOG_GITHUB_TOKEN=token
|
|
github_changelog_generator --base HISTORY.md --user python-kasa --project python-kasa --since-tag $PREVIOUS_RELEASE --future-release $NEW_RELEASE -o CHANGELOG.md --exclude-tags-regex 'dev\d$'
|
|
```
|
|
|
|
Remove '--exclude-tags-regex' for dev releases.
|
|
|
|
4. Commit the changed files
|
|
|
|
```bash
|
|
git commit -av
|
|
```
|
|
|
|
5. Create a PR for the release.
|
|
|
|
6. Get it merged, fetch the upstream master
|
|
|
|
```bash
|
|
git checkout master
|
|
git fetch upstream
|
|
git rebase upstream/master
|
|
```
|
|
|
|
7. Tag the release (add short changelog as a tag commit message), push the tag to git
|
|
|
|
```bash
|
|
git tag -a $NEW_RELEASE
|
|
git push upstream $NEW_RELEASE
|
|
```
|
|
|
|
All tags on master branch will trigger a new release on pypi.
|
|
|
|
8. Click the "Draft a new release" button on github, select the new tag and copy & paste the changelog into the description.
|