chore: Warn users to force update if innounp is on version 2025

[z-Fng]

Description

This PR makes the following changes:

• chore: Warn users to force update if innounp is on version 2025

Motivation and Context

Innounp was previously incorrectly updated to version 2025 (ScoopInstaller/Main@64a7d914ab). Since this version number is higher than the actual latest version (currently 2.67.4), it blocks the automatic update process and has led to more frequent decompression errors.

Workaround for ScoopInstaller/Scoop#6572 and ScoopInstaller/Scoop#6595 (comment).

Related Issues

• ollama-full@0.15.5: decompress error Extras#17156
• [Resolved]: gimp@3.0.8-1: decompress error Extras#17152
• xmedia-recode@3.6.2.1: decompress error Extras#17082

Testcase

• ollama-full@0.17.4: decompress error z-Fng/Scoop-Extras#18

Summary by CodeRabbit

• Documentation
  • Updated help guidance for package installation and update procedures with clearer command instructions.
  • Added detailed explanation addressing a known version compatibility issue, including step-by-step workaround instructions for affected users.
  • Enhanced and preserved existing explanatory content and warning messages for comprehensive user support.

[coderabbitai]

Walkthrough

Updated the Show-ExtractionHelpTips function in src/Action/Issue/Extraction.psm1 to modify innounp update guidance. Changed update commands to include the -f forced flag and added a note documenting a 2025-era version that caused automatic update issues.

Changes

Cohort / File(s)	Summary
innounp Update Guidance src/Action/Issue/Extraction.psm1	Added forced update flag (-f) to innounp and innounp-unicode update commands; added explanatory note for a historical version quirk affecting affected users.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: Improve help tips for decompress errors #68: Modified the same Show-ExtractionHelpTips function to update innounp guidance with forced updates and historical version notes.
• feat: Provide help tips for decompress error issues #62: Changed innounp help text within the same Show-ExtractionHelpTips function.

Suggested reviewers

• deevus
• niheaven

Poem

🐰 A quirky version, foiled our dreams in twenty-twenty-five,
But now with -f flags, the bunny updates come alive!
Forced and faithful, the guidance gleams so bright,
Historical hiccups smoothed with helpful might. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a warning for users with innounp version 2025 to force update, which is the core purpose of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/Action/Issue/Extraction.psm1`:
- Around line 113-114: Update the NOTE text that currently references only
`innounp` to explicitly state whether `innounp-unicode` is also affected; if
both are affected, change the note string (the array element containing the '>
[!NOTE]' paragraph) to mention both `innounp` and `innounp-unicode` and include
both recovery commands (`scoop update innounp -f` and `scoop update
innounp-unicode -f`); if only `innounp` is affected, update that same note to
explain why `innounp-unicode` is still listed in the main instructions (for
example, it was included for completeness or is unaffected) so readers know
whether they need to run `scoop update innounp-unicode -f` as well.

🧹 Nitpick comments (1)

src/Action/Issue/Extraction.psm1 (1)

108-115: Consider scoping -f advice to the affected version only.

The -f flag is now unconditionally recommended for all users in the code-block commands (lines 108, 111), even those not on the problematic 2025 version. While harmless, this is a heavier recommendation than necessary for unaffected users. Consider keeping the general advice without -f and reserving the force-update instruction for the NOTE block that specifically targets the 2025 version:

Suggested restructuring

             '  ```',
-            '  scoop update innounp -f',
+            '  scoop update innounp',
             '  ```',
             '  ```',
-            '  scoop update innounp-unicode -f',
+            '  scoop update innounp-unicode',
             '  ```',
             '> [!NOTE]',
-            '> Innounp was previously incorrectly updated to version [2025](https://github.com/ScoopInstaller/Main/commit/64a7d914ab). Since this version number is higher than the actual latest version, it prevents automatic updates. If you are on this version, please run `scoop update innounp -f`.',
+            '> Innounp was previously incorrectly updated to version [2025](https://github.com/ScoopInstaller/Main/commit/64a7d914ab). Since this version number is higher than the actual latest version, it prevents automatic updates. If you are on this version, please run `scoop update innounp -f` or `scoop update innounp-unicode -f` instead.',

This way the general advice stays lightweight, and only affected users are directed to force-update.

[z-Fng]

cc @ScoopInstaller/maintainers Could we merge this? (I don't have write access to this repository.)