chore: update ecosystem test expectations for current canary#660
Merged
magurotuna merged 2 commits intoJul 9, 2026
Conversation
…stry state sonner: the TS2552 related-information snippet quotes CloseEvent's declaration, whose text changed in denoland/deno#35639. mebus/ipinfo: npm types resolution verdicts flipped (registry-state drift, not canary) — see denoland#659. Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Y719WzyQa6YUAJsvAB6wP1
The 1_0_1 update missed the other stale versions in the same packages (ipinfo/client 1_0_2-1_0_7, mebus/mebus 1_0_2); same 2.8->2.9 canary drift, all TYPE CHECK FAILED -> PASSED. Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Y719WzyQa6YUAJsvAB6wP1
magurotuna
changed the title
avocet-bot
approved these changes
Jul 9, 2026
avocet-bot
left a comment
avocet-bot
left a comment
There was a problem hiding this comment.
LGTM. Snapshot-only refresh matches the current canary behavior; ecosystem + CI checks are green.
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
2 participants
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.
Refreshes the ecosystem snapshots that are currently red on CI (surfaced on #658, 2026-07-09). Regenerated with
UPDATE=1 cargo test --test ecosystem <spec>against canary4064da2bee25c414481dc7985e474b62da497066, and verified green withoutUPDATEafterwards.Specs refreshed:
bureaudouble/[email protected]ipinfo/[email protected]…1.0.7mebus/[email protected],@1.0.2All are canary drift, not registry drift (an earlier attribution in #659 was wrong — see the correction comment there):
bureaudouble/[email protected]— bisected to refactor(tsc): defer web-platform globals to lib.dom in deno libs deno#35639 ("defer web-platform globals to lib.dom in deno libs"): the error set (TS2304/TS2552) is unchanged, but the TS2552 related-information snippet quotesCloseEvent's declaration, whose text changed with the lib restructuring (declare var CloseEvent: { ... }→typeof globalThis extends ...form).ipinfo/clientandmebus/mebus—TYPE CHECK FAILED→PASSEDfrom the Deno 2.8 → 2.9 transition (npm types resolution improved:mebusno longer errors on[email protected]'s default import, TS1192;ipinfono longer errors on thepuppeteernamespace, TS2503). The minimal repro fails on Deno 2.8.3 (matching the old snapshots) and passes on 2.9.1+. The main ecosystem workflow has in fact been red for these since 2026-06-22 (last green: 2026-06-10) — it went unnoticed because it isn't a required check.Note: beyond the snapshot refresh, the process problem is that the ecosystem workflow stayed red on main for weeks without anyone noticing — #659's correction comment discusses that; this PR just brings the snapshots in line with what CI observes today.
Closes #659