Repository navigation
Bump jest and @types/jest - #5
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) and [@types/jest](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jest). These dependencies needed to be updated together. Updates `jest` from 29.7.0 to 30.4.2 - [Release notes](https://github.com/jestjs/jest/releases) - [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md) - [Commits](https://github.com/jestjs/jest/commits/v30.4.2/packages/jest) Updates `@types/jest` from 29.5.14 to 30.0.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jest) --- updated-dependencies: - dependency-name: jest dependency-version: 30.4.2 dependency-type: direct:development update-type: version-update:semver-major - dependency-name: "@types/jest" dependency-version: 30.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
walhalabi-code
added a commit
that referenced
this pull request
Aug 30, 2026
The suite fails on a fresh clone on Windows, and has since the repository was
created. Git's core.autocrlf is on by default there, so checkout rewrites text
files to CRLF; test/ai.test.ts asserts body.startsWith('---\n') on a generated
skill file, which is false once the bytes on disk are ---\r\n.
CI never saw it because Linux runners check out LF, and the maintainer's working
copy predates any checkout so it still holds the original LF. Only someone
cloning fresh on Windows hits it, which is to say a new contributor on their
first npm test.
The stored blobs are already LF, so this changes checkout behaviour only and no
file content moves.
Found while investigating why Dependabot PR #5 failed. That turned out to be
unrelated: its lockfile is out of sync with its package.json, so every job dies
at npm ci before a test runs. jest 30 itself is fine - 332 of 334 pass on it,
and the single failure is this line-ending bug, which reproduces identically on
jest 29.
Co-authored-by: Waseem Alhalabi <217769131+walhalabi-code@users.noreply.github.com>
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
walhalabi-code
added a commit
that referenced
this pull request
Aug 31, 2026
All five checks failed in under 40 seconds, which is the npm ci signature: it refuses a package.json and package-lock.json that disagree, and every job runs it before anything else. Making @types/parse a required peer rather than an optional one changed the dependency tree, and the lock was not regenerated to match: npm error Missing: @types/parse@3.0.9 from lock file This is the same failure diagnosed in Dependabot PR #5 earlier today - a lockfile out of step with its package.json, killing every job before a single test runs. Worth noting that the lesson did not transfer on the first try. Also picks up the 3.0.0 -> 3.0.1 version bump in the lock's root entry. Checked while regenerating: installing @types/parse alongside the library's own src/global.d.ts does not collide. That file is not shipped - dist carries no global.d.ts - so a consumer only ever sees @types/parse.
walhalabi-code
added a commit
that referenced
this pull request
Aug 31, 2026
* Act on the first round of hands-on testing Seven findings from using the published package the way a stranger would. @types/parse was declared an optional peer, but the shipped declarations require it: BaseModel is typed as extending Parse.Object. Without it, TypeScript reports "Cannot find namespace 'Parse'" and then "Property 'save' does not exist on type 'Note'" - errors that point at the user's own model rather than the missing package. It is now a required peer. psk new installs the generated project's dependencies. Scaffolding something that cannot run until you read the next line of output was a needless step. --no-install opts out; a failed install warns and puts the step back in the next-steps list rather than leaving a project that looks finished. The generated project can be tested. It had no runner, no example and no test script, which sat badly against a library that argues for verification. It now uses Node's own runner - nothing to install, no config - and ships five tests covering the failures that raise no error: that a field written on a model actually reaches Parse, that save() would send it, and that the schema rules are enforced. npm audit is clean in a new project. The 14 advisories all came from transitive pins in parse-server's tree, none of them fixable by bumping a peer because parse 8.6.0 is the latest and pins ws exactly. Overrides to the patched versions of ws, follow-redirects, ip-address and uuid take it to zero. Verified that parse-server still loads and the project still builds under them. listNotes demonstrates real pagination. It returned results.length as the count - the size of the page you already have, which tells a client nothing. It now uses withCount() for the true total in one round trip, and returns limit, skip and hasMore. The CLI no longer describes itself as broken. "The mistakes this library fails silently on" was meant as "mistakes that produce no error", but it parses as "this library fails silently" - printed after every psk new. The mistake is now the subject, not the library. psk new says something when it lands inside another npm project, and seed.ts is 254 lines rather than 325, with the same behaviour and half the commentary. Docs, website and the generated README follow the CLI: six quickstart blocks, the --no-install flag, a Tests section, corrected file counts, and the search index, which duplicates page text and had gone stale again. 334 library tests pass. A generated project compiles, passes its own five tests, and audits clean. * Regenerate the lockfile for the required @types/parse peer All five checks failed in under 40 seconds, which is the npm ci signature: it refuses a package.json and package-lock.json that disagree, and every job runs it before anything else. Making @types/parse a required peer rather than an optional one changed the dependency tree, and the lock was not regenerated to match: npm error Missing: @types/parse@3.0.9 from lock file This is the same failure diagnosed in Dependabot PR #5 earlier today - a lockfile out of step with its package.json, killing every job before a single test runs. Worth noting that the lesson did not transfer on the first try. Also picks up the 3.0.0 -> 3.0.1 version bump in the lock's root entry. Checked while regenerating: installing @types/parse alongside the library's own src/global.d.ts does not collide. That file is not shipped - dist carries no global.d.ts - so a consumer only ever sees @types/parse. --------- Co-authored-by: Waseem Alhalabi <217769131+walhalabi-code@users.noreply.github.com>
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.
Bumps jest and @types/jest. These dependencies needed to be updated together.
Updates
jestfrom 29.7.0 to 30.4.2Release notes
Sourced from jest's releases.
... (truncated)
Changelog
Sourced from jest's changelog.
... (truncated)
Commits
746f2a0v30.4.2b3b4a09v30.4.15cbb21ev30.4.0db7141afix: allowcollectCoverageandcoverageProviderin project config (#16132)efb59c2v30.3.096c53d3feat(jest-config): adddefineConfigandmergeConfigfunctions (#15844)855864ev30.2.0da9b532v30.1.3ebfa31cv30.1.2d347c0fv30.1.1Updates
@types/jestfrom 29.5.14 to 30.0.0Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)