ipatool: Add version 2.3.0#7705
Conversation
|
Your changes did not pass all checks. Please address the issues in the manifest and comment starting with Invalid manifests
|
|
I see GITHUB API RATE LIMIT as the cause of check failure |
This is a json schema validation error, not a GitHub rate limiting issue.
|
|
Where do you see this error? And why did local checks/manifest autoformatting and app updates not catch it? Where did the update get the hash from then? But more importantly, how do you check hashes if they're in different per-architecture files? Or did the tool just ignore that value and those custom files and calculated hash from github itself? |
|
It seems it's not needed indeed, guess it's auto-calculated from github, so I've just removed the hash key |
From the CI logs and the VSCode JSON plugin.
If necessary, the hash field should be nested under the architecture field, not the other way around. Lines 21 to 32 in 519155f |
|
I see, thanks, I was only checking the links that the bot mentioned as failing, wonder why it didn't link to the logs you did. |
The log output is a bit of a mess. |
|
/verify
|
|
All changes look good. Wait for review from human collaborators. ipatool
|

Closes #7704
<manifest-name[@version]|chore>: <general summary of the pull request>