Bump mocha from 10.8.2 to 11.7.6 in /packages/databricks-vscode#1964
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump mocha from 10.8.2 to 11.7.6 in /packages/databricks-vscode#1964dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Contributor
|
🤖 Integration tests ❌ 3 of 4 test jobs failed for |
Bumps [mocha](https://github.com/mochajs/mocha) from 10.8.2 to 11.7.6. - [Release notes](https://github.com/mochajs/mocha/releases) - [Changelog](https://github.com/mochajs/mocha/blob/v11.7.6/CHANGELOG.md) - [Commits](mochajs/mocha@v10.8.2...v11.7.6) --- updated-dependencies: - dependency-name: mocha dependency-version: 11.7.6 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/packages/databricks-vscode/mocha-11.7.6
branch
from
99024af to
19320ad
Compare
Contributor
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Contributor
|
🤖 Integration tests ❌ 3 of 4 test jobs failed for |
rugpanov
added a commit
that referenced
this pull request
Jul 6, 2026
## Why Dependabot #1964 bumped `mocha` to 11.7.6, but the one-line `package.json` change **fails CI**. mocha is consumed via the `ts-mocha` wrapper, whose `^10.0.0` pin peer-caps mocha at `^10.X.X`, so the bump produces a peer-dependency conflict (reproduced locally by applying the PR verbatim): ``` YN0060: databricks provides mocha 11.7.6, which doesn't satisfy what ts-mocha requests ``` CI installs with `yarn install --immutable` (`unit-tests.yml`, `push.yml`, `create-build-artifacts.yml`, `release-pr.yml`), so the stale/conflicting lockfile makes the install step fail outright — which is why #1964 is BLOCKED. ## What - Bump `mocha` `^10.2.0` → `^11.7.6` (the Dependabot change). - Bump `ts-mocha` `^10.0.0` → `^11.1.0` (latest), whose peer range now includes `^11.X.X`. - Regenerate `yarn.lock`. Notes for the reviewer: - **ts-mocha 11 moved `ts-node` + `tsconfig-paths` from direct deps to peers.** The extension already declares `ts-node@^10.9.2` (satisfies the peer) and `tsconfig-paths` is an *optional* peer — so no additions are needed. - `@types/mocha@^10.0.6` is unchanged: `10.0.10` is still `latest` (no v11 types line; the mocha type API is stable). - `@wdio/mocha-framework@9.29.0` pulls its **own** `mocha@^10.3.0` as a *direct* dependency, so the e2e/wdio path is unaffected and keeps mocha 10 internally. - Engine: mocha 11 requires node `^18.18 || ^20.9 || >=21.1`; the extension requires `node >=22.0`. Dev-only dependency — no runtime, extension-behavior, or shipped-output change for users. ## Verification - `yarn install --immutable` passes (no `YN0028`, no `YN0060`). - `yarn run build` (`tsc --build`) succeeds. - `test:integ:sdk` (`ts-mocha --type-check`, `--dry-run`) type-checks and loads all `src/sdk-extensions/**/*.integ.ts` files and collects the suite. - `yarn run test:unit`: **268 passing, 0 failing** (mocha 11 `new Mocha` harness in `suite.ts`). - `eslint` clean on `suite.ts` and the mocha-consuming test files. Supersedes #1964 (which cannot merge without the `ts-mocha` bump). This pull request and its description were written by Isaac. --- <!-- GITHUB_MCP_FOOTER: This attribution is automatically appended by GitHub MCP. --> _This PR was created with [GitHub MCP](http://go/mcps)._
Contributor
|
already fixed |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/packages/databricks-vscode/mocha-11.7.6
branch
Merged
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
1 participant
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps mocha from 10.8.2 to 11.7.6.
Release notes
Sourced from mocha's releases.
... (truncated)
Changelog
Sourced from mocha's changelog.
... (truncated)
Commits
3765ba0chore(v11.x): release 11.7.6 (#5632)73ebdfafix(test): replacewmicusage with native Windows API (#5694)aafe6fdfix: makedescribe().timeout()work0696784chore: format all code (#5629)8d01d33chore: remove Netlify (#5630)9a6a5dbchore(v11.x): release 11.7.5 (#5523)8b21b38chore: run tests on PRs for and pushes to v11.x (#5525)663fff4chore: setup release-please for v11 (#5522)8d97220Update release-please to include v11.x and use Node ^22d89dbaffix: swallow morerequireerrors from *ts files (#5498)