You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This upgrade contains a high-risk major version update for tap and a low-risk patch update for typeorm.
tap 11.1.5 → 18.0.0 (HIGH)
This is a significant upgrade across 7 major versions, introducing substantial breaking changes. Tests written for v11 will require significant refactoring to work with v18.
Key Breaking Changes:
Execution Model: Test files now run in separate processes by default, which can affect tests that rely on shared state.
Coverage Reporting: The nyc dependency has been replaced with c8. Coverage is now enabled by default, and missing coverage is treated as a test failure. Many CLI flags like --cov, --no-cov, and --check-coverage have been removed or replaced.
Configuration: Configuration via test-regex is replaced by include/exclude glob patterns. The CLI has been overhauled, with commands like tap report and tap replay replacing older flags.
API & Plugins: Functionality previously built-in is now handled by plugins (@tapjs/typescript, @tapjs/mocha-globals). Assertion synonyms (e.g., t.is_not_equal()) have been removed.
Node.js Support: Support for all Node.js versions below 16.x has been dropped.
Recommendation:
This upgrade requires a dedicated effort to migrate test suites. Developers must review the official upgrade guide, refactor test configurations, update CI/CD scripts to use the new CLI commands, and adapt tests to the new plugin-based architecture and assertion APIs.
This is a minor update within the same major version. The changelogs indicate that this range consists primarily of bug fixes and minor feature enhancements. No breaking API changes are documented for this specific version span.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
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
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.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-JSYAML-17342520
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.