build: bump icloudpy to 0.9.0 — fixes headless 2FA push#471
Merged
Conversation
icloudpy 0.9.0 adds trigger_2fa_push_notification (mandarons/icloudpy#138). The documented `docker exec ... icloud --username` re-auth flow now pushes a 2FA code to the user's trusted devices when two-step auth is required, instead of stalling. Verified end-to-end: code pushed, validated, session trusted. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Splitting the pure fix out of #470 per request — this is the optional-Telegram-free part.
Bumps icloudpy
0.8.0→0.9.0, which addstrigger_2fa_push_notification(icloudpy #138). The documenteddocker exec … icloud --usernamere-auth flow now pushes a 2FA code to your trusted devices when two-step auth is required, instead of stalling with no code.Verified end-to-end: on 0.9.0 the CLI triggered the push, the code validated, and the session was trusted (HSA-TRUST cookie written).
#470 will be rebased down to just the optional Telegram convenience layer on top of this.