Release 4.5.13

[ekutner]

Is there an existing feature request for this?

• I have searched the existing issues

Your feature request

I don't want to be pushy but it's been two months since 4.5.12 was released and there have been many important improvements since. Maybe consider releasing 4.5.13 so that those of us who are using the AppDaemon Home Assistant Add-on can get those improvements?
I know there are workarounds and ways to get the latest code, it's just much more convenient when it's in the add-on.

[hugh-martin]

Did you see this? #2495

[jsl12]

Looks like it's finally time to write that doc section.

[ekutner]

@hugh-martin my bad, I wrongly assumed that if there would be something that mentioned 4.5.13 it would be in an open issue, so I filtered for those and didn't see #2495 which was closed. I even checked the discord server but it seemed mostly abandoned, with the last announced release being 4.5.1, so I assumed no one was following it.
The workaround discussed in that thread is nice, but it's not an acceptable way to run a production server, because every restart it will pull dev again and potentially break something unexpected. It took quite a while to discover and fix everything that broke in the transition from 4.4 to 4.5 and I don't what things changing under the hood unexpectedly. For now, I already have the critical bugs I care about, monkey patched in my apps but I still prefer a stable release with them. That would be much cleaner.

[cebtenzzre]

every restart it will pull dev again

True. My approach has been to pin to a specific commit, such as beaa161, instead of the dev branch itself. E.g.,

system_packages: []
python_packages: []
init_commands:
  - pip uninstall -y appdaemon
  - pip install https://github.com/appdaemon/appdaemon/archive/beaa1616e2c68437289f9f7f9fb9434de1063c50.zip

Pinning to a commit is the typical way to pull in changes from a repo that has not released them yet.

[ekutner]

@cebtenzzre good idea, thanks.

[jsl12]

This will all be included in the forthcoming doc page, but you can specify the short hash version of the commit in that syntax. Currently the latest hash is git+https://github.com/AppDaemon/appdaemon@beaa161

Pip itself will use git to process requirements (works with both URLs and local directories). Because the package name in git will match the appdaemon that's already installed in the add-on, specifying it this way will cause it to be replaced with the git version.

[tivoo]

Trying your workaround @cebtenzzre gives me:
ERROR: HTTP error 404 while getting https://github.com/appdaemon/appdaemon/archive/refs/heads/beaa1616e2c68437289f9f7f9fb9434de1063c50.zip ERROR: Could not install requirement https://github.com/appdaemon/appdaemon/archive/refs/heads/beaa1616e2c68437289f9f7f9fb9434de1063c50.zip because of HTTP error 404 Client Error: Not Found for url: https://codeload.github.com/AppDaemon/appdaemon/zip/refs/heads/beaa1616e2c68437289f9f7f9fb9434de1063c50 for URL https://github.com/appdaemon/appdaemon/archive/refs/heads/beaa1616e2c68437289f9f7f9fb9434de1063c50.zip [20:31:25] FATAL: Failed executing init command: pip install https://github.com/appdaemon/appdaemon/archive/refs/heads/beaa1616e2c68437289f9f7f9fb9434de1063c50.zip
Any idea when this release will actually be available to not try and make this workaround work? Thanks!

[cebtenzzre]

Trying your workaround @cebtenzzre gives me:

Sorry, typo. Edited.