Releases: dhleong/ps4-waker
Releases · dhleong/ps4-waker
1.10.1
1.10.0
1.9.0
Notes:
Functionally, this release just updates dependencies to resolve npm audit
warnings, but I'm dropping official support for Node 6 so the minor release
version number got bumped. I haven't changed any configs so it should still
work, but we won't be testing against it in CI builds anymore, since it's quite
old now, and any issues that pop up will be resolved with "upgrade Node."
1.8.6
Bug Fixes:
- Relinquishing root permissions too early (#118)
- Treat passcode errors as fatal (always exit when seen)
- Fix args handling for pin command (implicit and explicit)
- Disallow --skip-login flag with incompatible commands
- Properly wait for Device to be closed instead leaving promise hanging
- Fix --pass flag
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
Enhancements:
- Attempt to automatically request root privileges, then drop asap (see Notes)
Bug Fixes:
- If a user is auth'd but has not entered the pin-code, ps4-waker will get into a weird state (#113)
Notes:
- Refactored CLI code (#108, #114). This shouldn't matter for most users, but ought to simplify future development. It also helped to resolve a bug (see above)
- I've seen many users run into issues using ps4-waker with sudo on a raspberry pi. Automatically relaunching with sudo seems weird and may be an antipattern, but it allows us to automatically de-escalate privileges and ensure that the credentials file is created in the expected location and with the expected permissions. I'm hoping that nobody in the future will have to manually mess with sudo, and that the number of issues created as a result of that will go to zero. I've tried to be very transparent in how we invoke sudo as well, and especially suspicious people can just
ctrl-c
out of it, or use--failfast
to avoid it. - 1.8.1 just removes a spurious console.log. Derp.
1.8.0
Enhancements:
- Attempt to automatically request root privileges, then drop asap (see Notes)
Bug Fixes:
- If a user is auth'd but has not entered the pin-code, ps4-waker will get into a weird state (#113)
Notes:
- Refactored CLI code (#108, #114). This shouldn't matter for most users, but ought to simplify future development. It also helped to resolve a bug (see above)
- I've seen many users run into issues using ps4-waker with sudo on a raspberry pi. Automatically relaunching with sudo seems weird and may be an antipattern, but it allows us to automatically de-escalate privileges and ensure that the credentials file is created in the expected location and with the expected permissions. I'm hoping that nobody in the future will have to manually mess with sudo, and that the number of issues created as a result of that will go to zero. I've tried to be very transparent in how we invoke sudo as well, and especially suspicious people can just
ctrl-c
out of it, or use--failfast
to avoid it.