New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bumped py17track to 2.1.0 #18804

merged 1 commit into from Nov 29, 2018


None yet
3 participants

bachya commented Nov 29, 2018


Bumps py17track to 2.1.0. Changelog:

Related issue (if applicable): fixes #18670

Pull request in with documentation (if applicable): N/A

Example entry for configuration.yaml (if applicable):

  - platform: seventeentrack
    username: !secret 17track_email
    password: !secret 17track_password


  • The code change is tested and works locally.
  • Local tests pass with tox. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.

If the code communicates with devices, web services, or third-party tools:

  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New or updated dependencies have been added to requirements_all.txt by running script/

This comment has been minimized.


balloob commented Nov 29, 2018

Why the WIP?

@bachya bachya changed the title from WIP: Bumped py17track to 2.1.0 to Bumped py17track to 2.1.0 Nov 29, 2018

@balloob balloob merged commit ab4d0a7 into home-assistant:dev Nov 29, 2018

3 of 4 checks passed

continuous-integration/travis-ci/pr The Travis CI build is in progress
Hound No violations found. Woof!
WIP Legacy commit status override — see details
cla-bot Everyone involved has signed the CLA

@wafflebot wafflebot bot removed the in progress label Nov 29, 2018

@bachya bachya deleted the bachya:17track-fix branch Nov 29, 2018

balloob added a commit that referenced this pull request Nov 29, 2018

@balloob balloob referenced this pull request Nov 29, 2018


0.83.1 #18811

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