Skip to content

refactor: Bump jasmine from 6.1.0 to 6.2.0 #876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mtrezza merged 1 commit into from
Apr 16, 2026
Merged

refactor: Bump jasmine from 6.1.0 to 6.2.0 #876

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
"cross-env": "10.1.0",
"eslint": "10.2.0",
"globals": "17.5.0",
"jasmine": "6.1.0",
"jasmine": "6.2.0",
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 16, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

For jasmine npm package, what changed between v6.1.0 and v6.2.0 (especially breaking changes, Node.js engine requirements, and CLI behavior)?

💡 Result:

No changes between jasmine npm package v6.1.0 and v6.2.0 because v6.2.0 does not exist as of 2026-04-16. The latest version is v6.1.0, released on 2026-02-22. v6.1.0 updates the jasmine-core dependency to 6.1.0. No breaking changes specific to jasmine-npm v6.1.0. Node.js engine requirements remain Node 20, 22, and 24 (tested versions). No mentions of CLI behavior changes. For context on v6.1.0 (from v6.0.0): - Breaking changes (in v6.0.0): Node 18 no longer supported; only first config file loaded if multiple present; ConsoleReporter moved to @jasminejs/reporters. - New features (in v6.0.0): Console reporter respects NO_COLOR env var; compatibility with glob 10-13. - CLI behavior: npx jasmine init/examples/run unchanged per docs.

Citations:

Do not upgrade jasmine to v6.2.0—this version does not exist. The latest version is v6.1.0 (released 2026-02-22). Upgrading to a non-existent version will cause npm install to fail. Either revert to v6.1.0 or verify the intended target version.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 44, The package.json currently lists the non-existent
dependency version "jasmine": "6.2.0"; change the "jasmine" dependency value
back to a valid released version (e.g. "6.1.0") or the correct intended version,
save package.json, then run npm install (or npm ci and update the lockfile) to
ensure the dependency graph is consistent.

"mongodb-runner": "6.7.3",
"nodemon": "3.1.14",
"nyc": "18.0.0",
Expand Down
Loading