Add privacy manifest

[onevcat]

Currently, APNGKit is not tracking any user information, nor using any APIs that being required to be declare. So we just have an empty privacy manifest file for now in case that Apple is trying to detect it.

Fixes #143

[onevcat]

@CodiumAI-Agent /review

[CodiumAI-Agent]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the PR introduces a new privacy manifest file and updates the Swift package and podspec to include this new file. The changes are straightforward and limited to configuration and manifest files, which makes the review process less complex. However, ensuring the correctness of the manifest content and its integration requires some knowledge about Apple's privacy requirements and Swift package management.
🧪 Relevant tests	No
🔍 Possible issues	Possible Issue: The PrivacyInfo.xcprivacy file is empty, which might not be sufficient if future updates of the app include features that require privacy declarations. It's important to keep this file updated according to Apple's guidelines.
🔒 Security concerns	No

Code feedback:

---

relevant file	[email protected]
suggestion	Consider specifying the Swift language versions supported by the package in the swiftLanguageVersions attribute to ensure compatibility. This can help developers and CI tools to build the package with the correct Swift version. [medium]
relevant line	platforms: [.macOS(.v10_13), .iOS(.v12), .tvOS(.v12)],

---

relevant file	APNGKit.podspec
suggestion	It's recommended to specify the iOS, macOS, and tvOS deployment targets in the podspec to ensure the library does not get integrated into projects that do not support these minimum platform versions. [medium]
relevant line	s.resource_bundles = {"APNGKit" => ["Source/APNGKit/PrivacyInfo.xcprivacy"]}

---

relevant file	Source/APNGKit/PrivacyInfo.xcprivacy
suggestion	Ensure that the PrivacyInfo.xcprivacy file is updated as soon as any feature requiring privacy permissions is added. It's crucial for complying with Apple's App Store Review Guidelines. [important]
relevant line

---

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, require_can_be_split_review, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.