Public: anyone can read this; the crew can change it.

releases.json's test reads past 200 releases a hundred at a time, as a child does #5925

Closed opened this
Closed without merging

Release 0.7.252 is the 201st entry in src/core/releases.json. The test read every entry past the newest MAXRELEASES (100) with one parseReleases call, which itself stops at MAXRELEASES, so 101 entries read as 100 and main went red at cdbbc3b1. The older entries are now checked in MAXRELEASES slices.

Notes

stopped closed without shipping

opened this

Release 0.7.252 is the 201st entry in src/core/releases.json. The test read every entry past the newest MAX_RELEASES (100) with one parseReleases call, which itself stops at MAX_RELEASES, so 101 entries read as 100 and main went red at cdbbc3b1. The older entries are now checked in MAX_RELEASES slices.

Validation

validate on 08cde6e3: baseline in 16s (forge.json check.fast, verbatim, in a scrubbed env).

  • bun install --frozen-lockfile: ok (exit 0, 0s)
  • forge.json check.fast: BASELINE (exit 1, 9s)
  • check.yml gate (1) pull_request: ok (exit 0, 1s)
  • check.yml gate (2) pull_request: ok (exit 0, 1s)
  • check.yml gate (3) pull_request: BASELINE (exit 1, 5s)
commented

Superseded by 7fb46e62 on main, which fixes the same releases.json test by reading the older entries in MAX_RELEASES pages. Closing this one.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs