innounp: Update to version 2.70.1, fix autoupdate URL - #8327
Conversation
Upstream (jrathlev/InnoUnpacker-Windows-GUI) renamed release assets from a static innounp-2.zip to versioned filenames (innounp-267.zip, innounp-270.zip, ...), breaking the manifest's hardcoded url/autoupdate url with a 404. - Bump to the latest release, 2.70.1 - Point url/hash at the current asset (innounp-270.zip) - Fix autoupdate.url to use $majorVersion$minorVersion so future bumps track the new naming convention automatically (verified against both existing assets: 2.67.11 -> innounp-267.zip, 2.70.1 -> innounp-270.zip)
WalkthroughChangesInnoUnp release metadata
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closes #8330 |
|
/verify |
|
All changes look good. Wait for review from human collaborators. innounp
|
|
Thanks for fixing this for now. Was thinking about making this more stable to not use However even if the author used GitHub releases or tags they'd need to enable immutable releases or promise to not re-upload binaries to a given release (seems the earlier breakages were caused by them doing just that, and there is some evidence in commit history of re-uploading binaries without changing version, or for new patch versions) Tags are entirely mutable in Git, and both tags/releases are mutable by default in GitHub so not a huge guarantee either. If the author is committing binaries to Git (sigh) as the most reliable distribution mechanism, it does always have raw permalinks available by commit SHAs (with path), e.g If the amount of breakage from auto-updates or maintainer changes is greater than the frequency of needed updates, I wonder if better to turn auto-updates off? Ideas on Auto-updatesI thought perhaps something like this might work off the folder's commit ATOM feed at https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commits/master/innounp-2/bin.atom to capture the commit SHA and version, but even the commit comments don't include the correct version number ( (treat as pseudo-code, don't think the "checkver": {
"url": "https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commits/master/innounp-2/bin.atom",
"regex": "(?si)Grit::Commit/(?<commitsha>[0-9a-f]{40}).*?update.*? ((2)\\.(\\d+)(\\.(\\d+))?)",
"replace": "${3}.${4}.${5}"
},
"autoupdate": {
"url": "https://raw.githubusercontent.com/jrathlev/InnoUnpacker-Windows-GUI/$commitSha/innounp-2/bin/innounp-$majorVersion$minorVersion.zip"
}
Snippet from the commit feed for posterity: <?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xml:lang="en-US">
<id>tag:github.com,2008:/jrathlev/InnoUnpacker-Windows-GUI/commits/master/innounp-2/bin</id>
<link type="text/html" rel="alternate" href="https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commits/master/innounp-2/bin"/>
<link type="application/atom+xml" rel="self" href="https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commits/master/innounp-2/bin.atom"/>
<title>Recent Commits to InnoUnpacker-Windows-GUI:master</title>
<updated>2026-07-21T14:00:29Z</updated>
<entry>
<id>tag:github.com,2008:Grit::Commit/807426708fd4a7ab260ff0a1c09e239f53c97782</id>
<link type="text/html" rel="alternate" href="https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commit/807426708fd4a7ab260ff0a1c09e239f53c97782"/>
<title>
Update to 2.70
</title>
<updated>2026-07-21T14:00:29Z</updated>
<media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/40795066?s=30&v=4"/>
<author>
<name>jrathlev</name>
<uri>https://github.com/jrathlev</uri>
</author>
<content type="html">
<pre style='white-space:pre-wrap;width:81ex'>Update to 2.70</pre>
</content>
</entry>
<entry>
<id>tag:github.com,2008:Grit::Commit/09de682baeb9c6f3b103d85f411265de19c53665</id>
<link type="text/html" rel="alternate" href="https://github.com/jrathlev/InnoUnpacker-Windows-GUI/commit/09de682baeb9c6f3b103d85f411265de19c53665"/>
<title>
Update to 2.67.11
</title>
<updated>2026-07-13T15:01:51Z</updated>
<media:thumbnail height="30" width="30" url="https://avatars.githubusercontent.com/u/40795066?s=30&v=4"/>
<author>
<name>jrathlev</name>
<uri>https://github.com/jrathlev</uri>
</author>
<content type="html">
<pre style='white-space:pre-wrap;width:81ex'>Update to 2.67.11</pre>
</content>
</entry>
... |

Summary
innounp's download URL 404s: upstream (jrathlev/InnoUnpacker-Windows-GUI) renamed release assets from a staticinnounp-2.zipto versioned filenames (innounp-267.zip,innounp-270.zip, ...), breaking both the manifest'surlandautoupdate.url.2.70.1, and pointsurl/hashat the current asset (innounp-270.zip).autoupdate.urlto use$majorVersion$minorVersionso future version bumps track the new naming convention automatically — verified against both currently published assets:2.67.11→innounp-267.zip,2.70.1→innounp-270.zip.Test plan
innounp-270.zipdirectly and verified the sha256 hash matches the manifest.bin/checkver.ps1 -App innounpresolves cleanly to2.70.1against the updated manifest.bin/formatjson.ps1 -App innounpproduces no diff (formatting unchanged).scoop installfrom this manifest and confirmedinnounp.exeruns (innounp - the Inno Setup Unpacker, version 2.70.1 (2026-07-21)).