Repository navigation
chore: housekeeping baseline - #134
Merged
Merged
Conversation
added 5 commits
November 1, 2026 20:12
A non-builtin import in build.js fails on a PR, not on a tag.
setup-node v7 defaults it on and caches once package.json names a manager.
The plugin peers ^5 at 1.4; @vitest/* matched no direct dependency.
Two visitors count two; the day alone expires; no raw IP stored. Salt and timeout stay unpinned.
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.
The stamp rehearsal runs without
node_modules, so a non-builtin import inbuild.jsfails on a PR and not on a tag that cannot move. Token jobs turn the package-manager cache off, which setup-node v7 would otherwise enable ifpackage.jsonnamed a manager. vitest moves to 5 and its major holds go. Three worker tests run against a fake store and kill nine mutants, including two visitors counting as one; salt and timeout stay unpinned. Nothing here changesdocs/orworkers/counter.js, so a merge needs no deploy.