Repository navigation
Conversation
… on purpose - Go, Maven and NuGet date and flag every listed version, not the newest few: Go `.info` and Maven POM dates are asked once per version (bounded fan-out) and kept as `release-dates` state, so a warm lookup asks only about versions it has not seen, wherever they sort; NuGet reads every registration page. A failed date request, or a NuGet version the registration does not describe yet, marks the version unchecked, and policy holds an unchecked release under a positive wait instead of reading it as undated. - A `permitted` filter admits prereleases only when it asks for them: a regex that matches the prerelease part, or a range that names a prerelease. Negated and merely narrowing filters no longer do, which stops Maven `[1,2)` or PyPI `<3` letting betas through. - mise's `prerelease: true` is carried into the catalog and treated like a prerelease version, matching `github-releases`. - A `github-tags` lookup through mise-versions falls back to GitHub's own tag catalog when the mirror leaves a tag undated, so annotated tags are dated by their tagger as the docs promise.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
count-patchula | df0ca6d | Commit Preview URL Branch Preview URL |
Nov 15 2026, 11:02 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes from the lookup and datasource scan. Each one was letting through a release that policy should have held back.
Invariant
Every version the lookup could propose is either dated and flagged by its source, or marked
unchecked. A positivewaitHoursholds anuncheckedrelease instead of treating it as undated. It shows up in the report as a notice, and a later lookup asks about it again. A missing answer can no longer skip the release-age wait.Fixes
Version::unchecked(catalog.rs) and arelease-datesstate (dates.rs). The state keeps each registry answer per version: a date, or "cannot be served". It is keyed by package and, for Maven, by the operator registry entry's scope..infoand Maven POMHEADrequests go only to versions with no stored answer, wherever they sort, with a boundedbuffer_unorderedfan-out of 8.guide/sources.md's ".info for new versions only" true..ok()?.GO_DATED_RELEASES, Maven'sDATED) is gone, and so arereached_knownand the head-stoppingmerge().nuget-registrationv2 lists them all), up to 4 at once.permittedfilter admits prereleases only when it asks for them (lookup/src/lib.rs,config/src/matching.rs).Filter::asks_for_prereleaseimplements three rules:regex:asks when it matches the prerelease but not the same version without its prerelease part (regex:-rc\.andregex:nightlyask;regex:^2\.does not).semver:range asks when it names a prerelease version itself and matches (semver:>=3.0.0-rc.1andsemver:[1.0-beta1,2)ask;semver:[1,2)andsemver:<3do not).guide/lookup-policy.mdandconfiguration.md.nightly-pinsexample (regex:-nightly\.) keeps working.mise()now carriesprerelease: trueintoVersion::prerelease, and the lookup treats it like a prerelease version, including for the current version,latest, and dist-tag targets. This matchesgithub-releases.tags.jsonhas a tag thatreleases.jsondoesn't date, thegithub-tagslookup falls back to GitHub's own tag catalog. That path dates annotated tags by their tagger and is cached byTagCatalog/TagObject.guide/lookup-policy.mdalready promised this;guide/sources.mdnow says how..infofetches run in parallel with a bounded fan-out, as part of fix 1.Cache and version bookkeeping:
catalog.rsandconfig/srcare hashed sources, so every derived representation and state that lists them got a version bump, and its row intests/derived-versions.tsv/tests/state-versions.tsvwas updated.release-datesis intests/state-exempt.tsv, since it holds facts about immutable releases.internals/cache.mddescribes the new state.Tests
datasource/tests/go_proxy.rs:.inforequests;.infoleaves the version unchecked and is retried.datasource/tests/sources.rs:6.0.5+build(yanked, dated);datasource/tests/versions_host.rs: an annotated tag the mirror leaves undated gets its tagger date through GitHub.datasource/tests/mise_lookup.rs:prereleases_stay_in_the_catalog_for_the_policy_to_decidenow asserts that the flag is carried (jq1.7rc2, prettier alphas), and that it is absent on stable releases.lookup/tests/policy.rs:!regex:^3\.,regex:^2\.and!semver:>=3admit no rc;regex:-rc\.andsemver:>=2.2.0-rc.1do;semver:[1,2)admits no beta;semver:[1.5-beta1,2)andregex:-betado;semver:<3admits no rc;semver:>=2.2.0rc1,<3does;waitHours = 0.cargo test -p patchula-config -p patchula-datasource -p patchula-lookup -p patchula-engine, and clippy-D warningson those crates pluspatchula-tools.Dropped
Nothing.
Follow-ups
releasestable (source = 'go') are no longer read. A later cache migration can drop them. I didn't add one here, to avoid colliding with other open cache migrations.github-tags.