Bump the npm_and_yarn group across 1 directory with 6 updates #50200
dependabot[bot]Annotations
17 errors and 28 warnings
|
Link Resolution Error:
/fake/message-test.md#L5
The link '/en/test/broken/link' could not be resolved in one or more versions of the documentation. Make sure that this link can be reached from all versions of the documentation it appears in. (Line: 5)
|
|
Link Resolution Error:
/fake/no-frontmatter.md#L5
The link '/en/missing/page' could not be resolved in one or more versions of the documentation. Make sure that this link can be reached from all versions of the documentation it appears in. (Line: 5)
|
|
Link Resolution Error:
/fake/test-file-2.md#L18
The link '/en/another/nonexistent/page' could not be resolved in one or more versions of the documentation. Make sure that this link can be reached from all versions of the documentation it appears in. (Line: 18)
|
|
Link Resolution Error:
/fake/test-file.md#L10
The link '/en/nonexistent/page' could not be resolved in one or more versions of the documentation. Make sure that this link can be reached from all versions of the documentation it appears in. (Line: 10)
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > mixed comment types in same block:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:242:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > empty lines and non-comment lines are ignored:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:219:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > non-annotate code blocks are ignored:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:199:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > indented comments are handled correctly:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:158:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > comments with multiple spaces after comment character fail:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:101:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > comments without space after comment character fail:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:49:26
|
|
src/content-linter/tests/unit/code-annotation-comment-spacing.ts > GHD045 - code-annotation-comment-spacing > correctly formatted comments pass:
src/content-linter/lib/init-test.ts#L35
TypeError: Cannot read properties of undefined (reading 'promises')
❯ runRule src/content-linter/lib/init-test.ts:35:29
❯ src/content-linter/tests/unit/code-annotation-comment-spacing.ts:27:26
|
|
src/content-linter/tests/integration/lint-cli.ts > Content Linter CLI Integration Tests > Default linter behavior > should respect rule filtering when specific rules are provided:
src/content-linter/tests/integration/lint-cli.ts#L140
AssertionError: expected 1 to be +0 // Object.is equality
- Expected
+ Received
- 0
+ 1
❯ src/content-linter/tests/integration/lint-cli.ts:140:24
|
|
src/content-linter/tests/integration/lint-cli.ts > Content Linter CLI Integration Tests > Default linter behavior > should verify default rule execution behavior:
src/content-linter/tests/integration/lint-cli.ts#L115
AssertionError: expected '\n> lint-content\n> tsx src/content-l…' to contain 'todocs-placeholder'
- Expected
+ Received
- todocs-placeholder
+
+ > lint-content
+ > tsx src/content-linter/scripts/lint-content.ts --paths /home/runner/work/docs/docs/content/test-integration/default-behavior-test.md
+
+
+ node:internal/modules/run_main:107
+ triggerUncaughtException(
+ ^
+ Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/runner/work/docs/docs/node_modules/markdownlint/lib/rules' imported from /home/runner/work/docs/docs/src/content-linter/lib/helpers/get-rules.ts
+ at finalizeResolution (node:internal/modules/esm/resolve:271:11)
+ at moduleResolve (node:internal/modules/esm/resolve:865:10)
+ at defaultResolve (node:internal/modules/esm/resolve:992:11)
+ at nextResolve (node:internal/modules/esm/hooks:785:28)
+ at resolveBase (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710816069:2:3744)
+ at async resolveDirectory (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710816069:2:4237)
+ at async resolve (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710816069:2:5355)
+ at async nextResolve (node:internal/modules/esm/hooks:785:22)
+ at async AsyncLoaderHooksOnLoaderHookWorker.resolve (node:internal/modules/esm/hooks:269:24)
+ at async handleMessage (node:internal/modules/esm/worker:251:18) {
+ code: 'ERR_MODULE_NOT_FOUND',
+ url: 'file:///home/runner/work/docs/docs/node_modules/markdownlint/lib/rules'
+ }
+
+ Node.js v24.16.0
+
❯ src/content-linter/tests/integration/lint-cli.ts:115:22
|
|
src/content-linter/tests/integration/lint-cli.ts > Content Linter CLI Integration Tests > Linter functionality verification > should detect errors when explicitly running search-replace rule:
src/content-linter/tests/integration/lint-cli.ts#L85
AssertionError: expected '\n> lint-content\n> tsx src/content-l…' to contain 'todocs-placeholder'
- Expected
+ Received
- todocs-placeholder
+
+ > lint-content
+ > tsx src/content-linter/scripts/lint-content.ts --paths /home/runner/work/docs/docs/content/test-integration/baseline-test.md --rules search-replace
+
+
+ node:internal/modules/run_main:107
+ triggerUncaughtException(
+ ^
+ Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/runner/work/docs/docs/node_modules/markdownlint/lib/rules' imported from /home/runner/work/docs/docs/src/content-linter/lib/helpers/get-rules.ts
+ at finalizeResolution (node:internal/modules/esm/resolve:271:11)
+ at moduleResolve (node:internal/modules/esm/resolve:865:10)
+ at defaultResolve (node:internal/modules/esm/resolve:992:11)
+ at nextResolve (node:internal/modules/esm/hooks:785:28)
+ at resolveBase (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710812020:2:3744)
+ at async resolveDirectory (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710812020:2:4237)
+ at async resolve (file:///home/runner/work/docs/docs/node_modules/tsx/dist/esm/index.mjs?1781710812020:2:5355)
+ at async nextResolve (node:internal/modules/esm/hooks:785:22)
+ at async AsyncLoaderHooksOnLoaderHookWorker.resolve (node:internal/modules/esm/hooks:269:24)
+ at async handleMessage (node:internal/modules/esm/worker:251:18) {
+ code: 'ERR_MODULE_NOT_FOUND',
+ url: 'file:///home/runner/work/docs/docs/node_modules/markdownlint/lib/rules'
+ }
+
+ Node.js v24.16.0
+
❯ src/content-linter/tests/integration/lint-cli.ts:85:22
|
|
audit-logs
Canceling since a higher priority waiting request for Test @ github:dependabot/npm_and_yarn/npm_and_yarn-e461afe22f exists
|
|
audit-logs
The operation was canceled.
|
|
Test
Canceling since a higher priority waiting request for Test @ github:dependabot/npm_and_yarn/npm_and_yarn-e461afe22f exists
|
|
events
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
data-directory
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
content-render
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
assets
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
webhooks
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
graphql
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
observability
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
color-schemes
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
content-linter
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
early-access
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
release-notes
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
versions
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
landings
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
products
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
archives
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
shielding
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
github-apps
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
rest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fixtures
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
secret-scanning
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
article-api
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
frame
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
workflows
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
redirects
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
automated-pipelines
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
search
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
search
Failed to restore:
|
|
audit-logs
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|