Skip to content

Restore behavior lost in #158 - #159

Merged
silverwind merged 2 commits into
masterfrom
fix-158-regressions
Aug 21, 2026
Merged

Restore behavior lost in #158#159
silverwind merged 2 commits into
masterfrom
fix-158-regressions

Conversation

@silverwind

Copy link
Copy Markdown
Owner

Fixes behavior regressions from #158, which turned several "skip this input" paths into throws or silent drops and narrowed matchers that were deliberately broad.

  1. CRLF workflow files yielded zero Docker dependencies
  2. exclude: ["*"], what a Renovate enabled: false maps to, stopped matching any name containing /
  3. Nested npm overrides collapsed onto one key, writing the wrong entry
  4. A spaced [workspace . dependencies] header aborted the whole run
  5. Out-of-tree go.work members were dropped, and one CRLF suppressed go.mod updates
  6. A pnpm default registry suppressed a scoped .npmrc registry, sending private names to the public registry untokenized
  7. Quoted Makefile image specs reported an update and wrote nothing
  8. A huge numeric Docker tag crashed the run
  9. Non-ENOENT filesystem errors aborted the run instead of skipping the member

Two expectations in #158 encoded the regressions rather than the intended behavior and are restored here.

Written by Claude (Opus 5).

silverwind and others added 2 commits August 21, 2026 20:04
#158 turned several "skip this input" paths into throws or silent drops,
and narrowed matchers that were deliberately broad. Dependencies went
missing from runs, some updates were reported but never written, and two
inputs aborted the run outright.

The widest ones: CRLF workflow files yielded zero Docker dependencies,
`exclude: ["*"]` (what a Renovate `enabled: false` maps to) stopped
matching any name containing a slash, nested npm overrides collapsed onto
one key so the wrong entry was written, and a spaced
`[workspace . dependencies]` header aborted everything.

A pnpm workspace default registry also suppressed a more specific scoped
`.npmrc` registry, which sent private package names to the public
registry without their token.

Two expectations in #158 encoded the regressions rather than the intended
behavior, so they are restored with the code.

Co-Authored-By: Claude (Opus 5) <noreply@anthropic.com>
The fixture simulates a real package root but omitted `"type": "module"`,
so Node 24 and 26 emitted MODULE_TYPELESS_PACKAGE_JSON on stderr and the
test's empty-stderr assertion failed. Node 22 does not warn, and a local
`--no-warnings` in NODE_OPTIONS hid it outside CI.

Co-Authored-By: Claude (Opus 5) <noreply@anthropic.com>
@silverwind
silverwind merged commit 7b24cbb into master Aug 21, 2026
14 checks passed
@silverwind
silverwind deleted the fix-158-regressions branch August 21, 2026 18:20
silverwind added a commit that referenced this pull request Aug 22, 2026
* update deps (silverwind)
* Keep hot-path reuse behavior-preserving (silverwind)
* Avoid redundant registry and Forge requests (silverwind)
* Take Docker Hub tag digests from the listing (silverwind)
* Stop a run stalling on rate limits and proxy fallbacks (silverwind)
* Restore version bumping for sha-pinned actions (silverwind)
* Cut redundant work from dependency lookup hot paths (silverwind)
* Restore behavior lost in #158 (#159) (silverwind)
* Close correctness gaps against Renovate and cut scope (#158) (silverwind)
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.

1 participant