Cut a release to include https://github.com/microsoft/keyper/pull/35
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing pull request #35 and the repository's release process for publishing to PyPI. Confirm that the fix supports non-UTF-8 plist decryption, then verify that a new PyPI release containing it is available.
Written by the indexing model from the issue text.
Description
Hi! I want to be able to use the fix added in https://github.com/microsoft/keyper/pull/35, so that I can implement decryping plist files from the FindMy app, which are non-utf8
Can you publish a release to pypi with this fix?
- Dominant language
- Python
- Stars
- 38
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/keyper
All issues in microsoft/keyper
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100