Skip to content

Pin the FindMy.py fork at its main branch - #207

Merged
parawanderer merged 1 commit into
mainfrom
chore/pin-fork-main
Sep 14, 2026
Merged

parawanderer merged 1 commit into
mainfrom
chore/pin-fork-main

Conversation

@parawanderer

Copy link
Copy Markdown
Owner

Repins the FindMy.py fork from bcb0787 to 07c919b in all four places (rule 14).

  • No code change. 07c919b has the same tree as bcb0787. The only commit between them merges parawanderer/FindMy.py#2, @LiamJ74's copy of the akd client info fix, opened a day before ours; the conflict was resolved to the code already there.
  • The pin now sits on the fork's default branch. The fork's main was fast-forwarded to the feature branch, so the pinned commit can't be orphaned by a branch being deleted or rewritten.

Co-authored by @LiamJ74 for the fix the pin points at.

Checked locally: the commit installs from GitHub, the Chaquopy bridge tests pass (294, including the pin-consistency tests), and the exporter suite passes (470 passed, 2 skipped).

🤖 Generated with Claude Code

The fork's main is fast-forwarded to the feature branch, so the pinned commit is
reachable from its default branch and cannot be orphaned by a branch being
deleted or rewritten. 07c919b has the same tree as the previous pin, bcb0787: the
only commit between them merges parawanderer/FindMy.py#2, @LiamJ74's copy of the
akd client info fix, opened a day before ours, with no code change.

Co-Authored-By: LiamJ74 <liam.comaille@gmail.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@parawanderer
parawanderer merged commit adae0bb into main Sep 14, 2026
8 checks passed

This branch was successfully deployed

1 active deployment
Android Build — 90e1edc5 Deployed Sep 14, 2026 by parawanderer via build #256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant