Skip to content

Releases: languitar/autosuspend

v3.1.3

29 Mar 19:36
Compare
Choose a tag to compare

3.1.3 (2021-03-29)

v3.1.2

29 Mar 19:23
Compare
Choose a tag to compare

3.1.2 (2021-03-29)

v3.1.1

28 Mar 19:01
Compare
Choose a tag to compare

3.1.1 (2021-03-28)

Bug Fixes

  • fix automatic version file generation (aeb601d)

v3.1.0

28 Mar 18:55
Compare
Choose a tag to compare

3.1.0 (2021-03-28)

Features

  • add semantic-release for automatic releases (ac5ec86)

Bug Fixes

  • use jsonpath ext to support filter expressions (24d1be1), closes #102

3.0

19 Jan 19:24
Compare
Choose a tag to compare
3.0

This version splits the executable into two distinct subcommands, one for activity checking and one for scheduling wake ups. This way, the wake up scheduling mechanism can be hooked into system tools such as systemd to ensure that wake ups are scheduled correctly every time the system suspends. This increases the reliability of the mechanism but also changes the way autosuspend has to be called. You now need to enable two systemd units as describe in systemd integration and the command line interface has changed.

2.0.6

11 Jul 19:21
v2.0.6
Compare
Choose a tag to compare

Maintenance release with a few fixes for checks and the wakeup function.

2.0.4

28 Jan 20:41
v2.0.4
Compare
Choose a tag to compare

Maintenance release to ensure that ActiveConnection handles IPv6 addresses with prefix correctly.

2.0.3

28 Jan 20:25
v2.0.3
Compare
Choose a tag to compare

A maintenance release to fix the activity check NetworkBandwidth, which did not update its internal state and therefore did not work as documented

2.0.2

10 Sep 20:02
v2.0.2
Compare
Choose a tag to compare

This is a maintenance release that fixes a few bugs with the Kodi checks and adds authentication support to them.

2.0.1

20 Jul 14:14
Compare
Choose a tag to compare

This is the first official release of the 2.x series. Apart from many detailed fixes and improvements, autosuspend is now also able to wake up a system in case of activities planned ahead of time. This requires some changes to existing configuration files and packaging needs to incorporate new upstream dependencies.

For a detailed list of changes and their implications, please refer to the changelog.