Skip to content

fix(checkver): Add opt-in skipdowngrade guard for manifests - #6720

Open
gitfool wants to merge 1 commit into
ScoopInstaller:developfrom
gitfool:fix/checkver-no-downgrade
Open

gitfool wants to merge 1 commit into
ScoopInstaller:developfrom
gitfool:fix/checkver-no-downgrade

Conversation

@gitfool

@gitfool gitfool commented Aug 19, 2026 •

Copy link
Copy Markdown

Description

checkver.ps1 -Update rewrites a manifest whenever the detected version differs from the manifest version, including when it is older. This adds an opt-in guard so a manifest can refuse a backwards rewrite.

The existing $update_available check (... -ne 0) only distinguishes "same" from "different" and feeds a console message; it never gated the actual write against direction, so a lower detected version was rewritten as if it were an update. This captures the comparison result, derives an explicit $version_regressed flag from it, and adds a per-manifest, opt-in guard keyed off checkver.skipdowngrade:

$comparison = [Scoop.VersionComparer]::Compare($ver, $expected_ver, (Get-UpdateNightlySetting))
$update_available = $comparison -ne 0
$version_regressed = $comparison -gt 0
...
# Opt-in guard: skip rewriting the manifest backwards unless forced.
if ($version_regressed -and $json.checkver.skipdowngrade -and !$ForceUpdate) {
    warn "${app}: skipping downgrade to $ver"
    continue
}

[Scoop.VersionComparer]::Compare already returns the correct direction for these cases (positive when the manifest is ahead of the detected version), including dash-suffixed nightly versions, so no comparison logic needed changing and $update_available keeps its existing meaning.

The guard is opt-in and off by default: default checkver behaviour is unchanged, so this cannot alter any existing manifest's updates unless its maintainer sets the flag. -ForceUpdate overrides the guard, matching how it already overrides the other version checks in checkver, so a deliberate downgrade is still possible.

Design

  • Opt-in, not opt-out. A new boolean checkver.skipdowngrade manifest property turns the guard on. Absent or false leaves the long-standing behaviour intact.
  • Maintainer-facing only. checkver.ps1 is a bucket-maintainer tool (run by the excavator / auto-pr), never by an end user installing a package, so the control lives in the manifest's checkver block alongside the other maintainer knobs (reverse, useragent, jsonpath, ...) and is documented in schema.json.
  • No new switch. Reuses the existing -ForceUpdate escape hatch rather than introducing a parameter.

Motivation and Context

Closes #6717

When an upstream source transiently reports a stale version, the excavator commits and pushes the downgrade to the bucket, from where it propagates to users. Recovery requires reset --hard plus a force-push, which then breaks scoop update for anyone who already pulled the bad commit (fatal: Not possible to fast-forward, aborting.).

In the case that prompted this, a nightly manifest versioned <semver>-<commit-count>-<sha> was moved from 10.8.1-5435-292018604 back to 10.8.1-5357-d63469107, i.e. 78 commits and three weeks backwards, and then repeatedly on subsequent scheduled runs. The trigger was upstream — GitHub's /actions/workflows/{id}/runs?event=push intermittently omitting recent runs (community/community#24626) — so the stale read is not Scoop's bug. The problem is that Scoop treats "different" as "newer" and offers no way to guard against it.

There is prior art for the directional-by-default-with-opt-out pattern on the client-side status path, still present in app_status:

Scoop/lib/core.ps1

Lines 570 to 576 in 20779c9

if ($status.version -and $status.latest_version) {
if (get_config FORCE_UPDATE $false) {
$status.outdated = ([Scoop.VersionComparer]::Compare($status.version, $status.latest_version, (Get-UpdateNightlySetting))) -ne 0
} else {
$status.outdated = ([Scoop.VersionComparer]::Compare($status.version, $status.latest_version, (Get-UpdateNightlySetting))) -gt 0
}
}

This change gives bucket maintainers an equivalent, explicit control for the checkver write path.

How Has This Been Tested?

Automated coverage added in test/Scoop-Checkver.Tests.ps1, tagged Scoop so it runs whenever PowerShell files change. The fixtures point checkver.url and autoupdate.hash.url at local files via file:// URIs, so the full checkver -Update round trip runs offline and deterministically with no network dependency:

  • source reports a newer version -> manifest updated
  • source reports an older version, skipdowngrade unset -> manifest downgraded (default behaviour, unchanged)
  • source reports an older version, skipdowngrade explicitly false -> manifest downgraded
  • source reports an older version, skipdowngrade true -> manifest unchanged, warning emitted
  • skipdowngrade true with -ForceUpdate -> downgrade permitted (override)
  • a guarded regression does not stop the remaining manifests being processed

That covers the three states of the flag (absent, false, true) plus the -ForceUpdate override. Verified locally on Windows 11 x64, PowerShell 7.6.5, Pester 6.2.0 (6/6 passing), rebased onto the latest develop with the [Scoop.VersionComparer] API.

Also confirmed Invoke-ScriptAnalyzer against PSScriptAnalyzerSettings.psd1 reports no findings for bin or test, and the new file satisfies the Scoop-00File.Tests.ps1 style constraints (CRLF, no BOM, trailing newline, no trailing whitespace, no leading tabs).

Manually reproduced against a real source with skipdowngrade enabled. Before the guard:

repro-app: 10.8.1-3788-2151290 (scoop version is 99.0.0) autoupdate available
Autoupdating repro-app
Found: 8564d283... using Github Mode
Writing updated repro-app manifest

and after:

repro-app: 10.8.1-3788-2151290 (scoop version is 99.0.0)
WARN  repro-app: skipping downgrade to 10.8.1-3788-2151290

Checklist:

  • I have read the Contributing Guide.
  • I have ensured that I am targeting the develop branch.
  • I have updated the documentation accordingly.
  • I have updated the tests accordingly.
  • I have added an entry in the CHANGELOG.

The schema.json property and the CHANGELOG entry are the documentation surfaces this change touches; there is no user-facing document describing checkver update semantics.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Adds an opt-in checkver.skipdowngrade flag that stops older detected versions from rewriting a manifest.

  • Manifests can skip updates when a source reports an older version.

No actionable issues found. Tests were inspected, not run.

Reviews (5) · Last reviewed commit: "fix(checkver): Add opt-in skipdowngrade ..." · Reviewed by Greptile

@coderabbitai

coderabbitai Bot commented Aug 19, 2026 •

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Summary by CodeRabbit

  • Bug Fixes

    • Prevented version checks from downgrading manifests when a lower source version is detected.
    • Added a warning when a downgrade is skipped.
    • Version checks now continue processing other manifests after skipping a regression.
    • Use -ForceUpdate to allow intentional downgrades.
  • Documentation

    • Added an unreleased changelog entry describing the downgrade-prevention fix.

Walkthrough

checkver.ps1 now distinguishes upgrades from regressions. It skips manifest downgrades and warns unless -ForceUpdate is used. Offline tests cover all update paths.

Changes

checkver downgrade prevention

Layer / File(s) Summary
Detect version direction
bin/checkver.ps1
The script stores the version comparison result and derives separate flags for available updates and regressed versions.
Guard manifest updates
bin/checkver.ps1, CHANGELOG.md
The script skips downgrades with a warning unless -ForceUpdate is enabled. The changelog records the fix.
Validate update behavior
test/Scoop-Checkver.Tests.ps1
Offline Pester fixtures verify upgrades, skipped downgrades, forced downgrades, and continued processing after a skipped downgrade.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the primary fix: preventing checkver from downgrading manifests.
Description check ✅ Passed The description directly explains the downgrade bug, the implementation, testing, and preserved ForceUpdate behavior.
Linked Issues check ✅ Passed The changes satisfy issue #6717 by blocking regressions, warning users, preserving upgrades and forced downgrades, and continuing processing.
Out of Scope Changes check ✅ Passed The changelog update and focused offline integration tests directly support the requested checkver fix and introduce no unrelated changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
bin/checkver.ps1 (1)

443-449: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add integration coverage for the new direction branches.

Cover these cases in the checkver tests:

  • A newer source version updates normally.
  • An older source version with -Update leaves the manifest unchanged and emits the warning.
  • -ForceUpdate permits the downgrade.
  • A skipped regression does not stop processing the next manifest.

The supplied Compare-Version tests in test/Scoop-Versions.Tests.ps1, Lines 64-71, do not verify this guard or its continue path.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c9cb1e95-7053-4003-b73b-7826a861930a

📥 Commits

Reviewing files that changed from the base of the PR and between cbd7c64 and eaa069f.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • bin/checkver.ps1

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

@gitfool

gitfool commented Aug 19, 2026

Copy link
Copy Markdown
Author

Add integration coverage for the new direction branches.

Good call — added in 95640c6 as a separate commit, covering exactly the four cases listed.

There was no existing harness for bin/ scripts (test/bin holds only the runners, and the only checkver references under test/ are formatter fixtures), so test/Scoop-Checkver.Tests.ps1 is new. The thing that made it worth doing rather than deferring is that checkver can be driven entirely offline: WebClient handles file://, so pointing both checkver.url and autoupdate.hash.url at local fixture files gives a complete, deterministic -Update round trip with no network dependency and no mocking. The hash fixture is a well-formed fake SHA-256, which is enough for autoupdate to resolve a hash via extract mode without downloading.

Tagged Scoop, so it runs whenever PowerShell files change, per test/bin/test.ps1.

To check the tests actually exercise the new branches rather than passing vacuously, I ran them against unpatched develop as well:

with the fix unpatched develop
newer version updates pass pass
older version left alone pass fail
-ForceUpdate downgrades pass pass
regression skip continues loop pass fail

The two guard-specific cases fail without the fix while the two controls still pass, which is the signature I wanted.

Verified on Windows 11 x64 / PowerShell 7.6.5 / Pester 6.1.0. Invoke-ScriptAnalyzer with PSScriptAnalyzerSettings.psd1 reports no findings for bin or test, and the new file satisfies the Scoop-00File.Tests.ps1 constraints.

You're also right that the Compare-Version cases in test/Scoop-Versions.Tests.ps1 don't cover this — they were cited only to note that the comparison primitive itself is already tested and unchanged by this PR, not as coverage for the guard.

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch 2 times, most recently from 2e2ffc9 to cc8247f Compare August 19, 2026 19:55
@gitfool

gitfool commented Aug 19, 2026

Copy link
Copy Markdown
Author

This is actively working as expected. My scoop-vpinball bucket has been running the excavator against this fork branch since #6717 was filed, and it's been correctly blocking the nightly version regressions every scheduled run while still allowing genuine updates through:

https://github.com/gitfool/scoop-vpinball/actions/runs/32251763617/job/96064166590

vpinball-nightly: 10.8.1-5357-d63469107 (scoop version is 10.8.1-5435-292018604)
WARN  vpinball-nightly: skipping downgrade to 10.8.1-5357-d63469107 (manifest is 10.8.1-5435-292018604)
vpinball-mingw-nightly: 10.8.1-5357-d63469107 (scoop version is 10.8.1-5435-292018604)
WARN  vpinball-mingw-nightly: skipping downgrade to 10.8.1-5357-d63469107 (manifest is 10.8.1-5435-292018604)

Also trimmed the warning message in the latest force-push — the "; source may be reporting a stale version" suffix was unnecessarily verbose for a log line that's already self-explanatory.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fcc85fba-8d5b-4c81-abb9-5d55644c3864

📥 Commits

Reviewing files that changed from the base of the PR and between 95640c6 and cc8247f.

📒 Files selected for processing (2)
  • bin/checkver.ps1
  • test/Scoop-Checkver.Tests.ps1

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Comment thread test/Scoop-Checkver.Tests.ps1 Resolved
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from cc8247f to 6eacf76 Compare August 19, 2026 19:59

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
test/Scoop-Checkver.Tests.ps1 (1)

53-75: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Assert the complete manifest state.

Get-ManifestVersion checks only version. The upgrade and forced-downgrade tests can pass while url or hash remain stale. The regression test can pass while a skipped update changes those fields. Read the full manifest and assert version, url, and hash; compare the complete pre/post manifest for the skipped case.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5ab70e19-bfc9-450b-8aa3-0e066ffd672e

📥 Commits

Reviewing files that changed from the base of the PR and between cc8247f and 6eacf76.

📒 Files selected for processing (1)
  • test/Scoop-Checkver.Tests.ps1

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

Comment thread test/Scoop-Checkver.Tests.ps1 Resolved
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from 6eacf76 to f8159c7 Compare August 19, 2026 20:05

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ab80262-8b73-4b5e-81dd-b9256ddca61b

📥 Commits

Reviewing files that changed from the base of the PR and between 6eacf76 and f8159c7.

📒 Files selected for processing (1)
  • test/Scoop-Checkver.Tests.ps1

Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.

Comment thread test/Scoop-Checkver.Tests.ps1 Resolved
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from f8159c7 to cf771f4 Compare August 26, 2026 19:46
@philippe-granet

philippe-granet commented Aug 30, 2026 •

Copy link
Copy Markdown

Blocking automatic downgrades by default makes sense as a safeguard against incorrect upstream version detection. However, I don’t think downgrades should be prohibited entirely.

A lower version is not necessarily less secure than a higher one. In the event of a compromised release or supply-chain attack, reverting to a previously verified version may be the safest remediation. The Trivy supply-chain incident illustrates this case: a newer release was malicious, so version ordering alone could not be used as a security or trust signal.

Could we keep this protection by default while providing an explicit override?

Reference: https://www.aquasec.com/blog/trivy-supply-chain-attack-what-you-need-to-know/

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch 4 times, most recently from 9a73d06 to 47d9ef1 Compare September 15, 2026 23:19
@niheaven

Copy link
Copy Markdown
Member

This is by design. The upstream may may withdraw the version release and delete the released artifacts, and Scoop always tracks the latest and downloadable version.

@gitfool

gitfool commented Sep 17, 2026

Copy link
Copy Markdown
Author

@niheaven if by design, it's actually undesirable/unwanted in my scenario, so it should at least be configurable.

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch 2 times, most recently from 1d055b8 to b39beed Compare September 26, 2026 21:20
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from b39beed to bd69f89 Compare September 29, 2026 05:58
@z-Fng

z-Fng commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

The upstream may may withdraw the version release and delete the released artifacts, and Scoop always tracks the latest and downloadable version.

I also find this design to be quite sound. This guarantees that in the event of a version rollback upstream, the manifest doesn't require manual intervention for users to install or update without issues (since the latest version is still functional); otherwise, manual edits to the manifest would be necessary. Below is a comparison between Scoop (which allows downgrades) and Homebrew (which disallows downgrades).

When an upstream source transiently reports a stale version, the excavator commits and pushes the downgrade to the bucket, from where it propagates to users. Recovery requires reset --hard plus a force-push, which then breaks scoop update for anyone who already pulled the bad commit (fatal: Not possible to fast-forward, aborting.).

Since the client side does not perform downgrades even if a version rollback occurs, in such cases you should not do a git reset --hard and force push. Currently, buckets do not support reset --hard when tracking a remote bucket.

if by design, it's actually undesirable/unwanted in my scenario, so it should at least be configurable.

It would be better to provide manifest-level or bucket-level options to allow customization, rather than changing the default behavior directly. This could help with edge cases (such as CDN cache inconsistencies, or in your scenario, inconsistent responses from the GitHub API) where no better checkver workaround is available (though in any scenario, I believe updating checkver should always be the preferred approach).

@gitfool

gitfool commented Sep 29, 2026

Copy link
Copy Markdown
Author

@z-Fng I have a homebrew tap for the same artifacts and like you say it does not have the same downgrade behaviour, which is good/better from my pov.

So are you proposing I should move the downgrade check to my bucket or manifest, more likely since the nightly is the only one with the issue, instead? How would I do that exactly? Are there buckets or manifests that already do this?

@niheaven

Copy link
Copy Markdown
Member

so it should at least be configurable.

I'll reconsider the proper method to handle this after v0.6.0 release.

@z-Fng

z-Fng commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

I have a homebrew tap for the same artifacts and like you say it does not have the same downgrade behaviour, which is good/better from my pov.

So are you proposing I should move the downgrade check to my bucket or manifest, more likely since the nightly is the only one with the issue, instead?

Yes. In my view, this is an edge case. There are also lots of examples of intended downgrades across official buckets. We shouldn't change the default behavior of checkver just for an edge case. Changing the default behavior would be a breaking change, requiring far more adaptation effort than the benefits it would bring.

How would I do that exactly? Are there buckets or manifests that already do this?

so it should at least be configurable.

This could help with edge cases (such as CDN cache inconsistencies, or in your scenario, inconsistent responses from the GitHub API) where no better checkver workaround is available.

Having manifest-level or bucket-level options would be a much better way to handle unintended downgrades.

BTW, from what I recall, there are indeed some tricky workarounds. For example, $expected_ver is accessible inside checkver.script (it's an undocumented variable, and might be removed in a future release).

@gitfool

gitfool commented Sep 29, 2026

Copy link
Copy Markdown
Author

Yes. In my view, this is an edge case. There are also lots of examples of intended downgrades across official buckets. We shouldn't change the default behavior of checkver just for an edge case. Changing the default behavior would be a breaking change, requiring far more adaptation effort than the benefits it would bring.

I could rewrite this to be opt-in and thereby keep the current default behaviour, but it sounds like you'd still prefer bucket/manifest-level config instead, and since that's not really supported (requires "workarounds") and not in the public api, then I'll just have to wait.

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from bd69f89 to c0c08fc Compare September 30, 2026 06:02
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from c0c08fc to 7ed4a98 Compare October 25, 2026 21:18
@gitfool gitfool changed the title fix(checkver): Don't downgrade manifest to older version fix(checkver): Add opt-in skipdowngrade guard for manifests Oct 25, 2026
@gitfool

gitfool commented Oct 25, 2026 •

Copy link
Copy Markdown
Author

@niheaven @z-Fng following up now that v0.6.0 has shipped. I've rebased onto the latest develop and rewritten this to be a manifest-level opt-in, as you both suggested.

The default behaviour of checkver is unchanged, so this is no longer a breaking change and the intended-downgrade manifests across the official buckets are unaffected. The guard only activates when a maintainer sets a new boolean checkver.skipdowngrade on a specific manifest (documented in schema.json, alongside reverse/useragent). -ForceUpdate still overrides it, so a deliberate downgrade remains possible. This keeps the edge case (the GitHub API inconsistency in my scenario, or CDN cache cases) handleable per-manifest without relying on the undocumented $expected_ver in checkver.script.

Squashed to a single commit; CI and the automated review are green on the new head. I've also updated the PR title and description to match.

@niheaven

Copy link
Copy Markdown
Member

Quick question: we already have a force_update flag in the config, which lets users keep their newer local version instead of downgrading to the bucket's. So why is a manifest-level trigger needed?

@gitfool

gitfool commented Oct 26, 2026

Copy link
Copy Markdown
Author

@niheaven I think force_update is a different layer and, if anything, works the opposite way to a downgrade guard.

It's client-side, in lib/core.ps1 app_status. With Compare-Version returning bucket-vs-installed:

  • default (force_update off): outdated = (… -gt 0), so scoop update only moves to a newer bucket version. A lower bucket version is ignored — this is what already lets a user keep their newer local version.
  • force_update on: outdated = (… -ne 0), so the client treats a differing bucket version as outdated too, i.e. it forces the install down to the bucket's lower version. That matches the config help, "Force apps updating to bucket's version."

So enabling force_update causes client-side downgrades rather than preventing them, and either way it only acts after the regression is already in the bucket.

What I want is upstream of all that: as the bucket maintainer I want to control and prevent downgrades from my side, at the source. checkver.skipdowngrade lives in bin/checkver.ps1, so it decides whether the excavator rewrites my manifest to a lower version when upstream transiently reports a stale one — before anything is committed, pushed, or reaches a user. As z-Fng noted, the client-side -gt 0 default does stop users installing a downgrade, but it doesn't stop the manifest in my bucket from being regressed in the first place, which is what this flag lets me opt out of per-manifest.

@niheaven

Copy link
Copy Markdown
Member

Yes, but from user side, they are the same: stop from installing a fallback/old version.

@gitfool

gitfool commented Oct 26, 2026

Copy link
Copy Markdown
Author

I didn't change the user side at all, and it's not relevant here. This is all about the maintainer side. I never want to downgrade the vpinball-nightly version in my bucket as this only happens due to unstable github artifacts.

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from 7ed4a98 to e2f2ba6 Compare October 29, 2026 04:50
@z-Fng

z-Fng commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

This keeps the edge case (the GitHub API inconsistency in my scenario, or CDN cache cases) handleable per-manifest without relying on the undocumented $expected_ver in checkver.script.

Providing a few examples where CDN cache inconsistency caused version flip-flopping, just for the maintainers' visibility. With this feature in place, we wouldn't have to bother with workarounds.

By the way, guess this should be considered a feature rather than a fix. Also, should we allow passing this as a global parameter (-SkipDowngrade) to the script?

@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch from e2f2ba6 to 7525a88 Compare November 6, 2026 22:45
@gitfool
gitfool force-pushed the fix/checkver-no-downgrade branch 2 times, most recently from 1773b3d to 387fe69 Compare November 14, 2026 03:06

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants