Bump websockets minimum version to 13

[epenet]

Fixes various deprecation warnings in Home Assistant

See https://websockets.readthedocs.io/en/stable/howto/upgrade.html

[chemelli74]

LGTM, thx !

[xchwarze]

@epenet if we are going to make a launch for HA we should see about integrating this one too #129

[epenet]

@xchwarze how are new packages deployed?
Is it a manual process on your end? or is it automated?

[epenet]

I assume it's currently manual, and we should look at implementing a CI pipeline:
https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/dependency-transparency

The package published to PyPi should be built and published inside a CI pipeline.

[epenet]

@epenet if we are going to make a launch for HA we should see about integrating this one too #129

I don't really understand the point of #129
In what context do you have this issue?
keep-alive should be handled automatically via PING-PONG

[xchwarze]

I assume it's currently manual, and we should look at implementing a CI pipeline: https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/dependency-transparency

The package published to PyPi should be built and published inside a CI pipeline.

Yes, as it is a library with few releases it was manual.

I don't really understand the point of #129
In what context do you have this issue?

As mentioned in the PR I noticed that every few hours the tv starts rejecting commands. Reject the first one and regenerate the session and it works again.
Where this is annoying is to turn the tv off as it looks like it is turned off but it is on.

keep-alive should be handled automatically via PING-PONG

When I started to do the POC to test a solution that was the first thing that came to my mind, I don't know if it's completely correct...

[xchwarze]

@epenet do you find any errors in this pipeline?

name: Publish to PyPI

on:
  push:
    tags:
      - 'v*'

jobs:
  publish:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout code
      uses: actions/checkout@v3

    - name: Set up Python
      uses: actions/setup-python@v4
      with:
        python-version: '3.10'

    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install build twine

    - name: Build package
      run: python -m build

    - name: Publish to PyPI
      env:
        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
      run: twine upload dist/*

[epenet]

I think it's now deprecated to use username/password
Even tokens should be migrated to trusted publishing.

Take a look at
https://github.com/pypa/gh-action-pypi-publish/tree/unstable/v1

[chemelli74]

@epenet do you find any errors in this pipeline?

You take a look at aiovodafone/aiocomelit

[xchwarze]

@epenet @chemelli74 I add a new workflow and generate with it a new release
https://github.com/xchwarze/samsung-tv-ws-api/blob/master/.github/workflows/release.yml

To use it you have to create the tag by cli and everything is generated by pipeline.

[epenet]

Great thanks!
Corresponding PR opened on Home Assistant: home-assistant/core#131690