Skip to content

Bump markdown-it from 12.3.2 to 14.2.0#1951

Merged
rugpanov merged 2 commits into
mainfrom
deps/markdown-it-v14
Jul 2, 2026
Merged

Bump markdown-it from 12.3.2 to 14.2.0#1951
rugpanov merged 2 commits into
mainfrom
deps/markdown-it-v14

Conversation

@rugpanov

@rugpanov rugpanov commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Why

Replaces Dependabot's #1946, which couldn't merge: its lockfile pinned linkify-it@5.0.2 — a version that doesn't exist on the public npm registry (latest is 5.0.1) — so yarn install --immutable failed in CI with a JFrog 403 (nothing upstream to serve). This PR regenerates the lockfile against real, published versions and takes the markdown-it major upgrade deliberately.

What

  • Bump markdown-it to ^14.2.0.
  • Regenerated yarn.lock resolves to real versions: markdown-it 14.2.0, linkify-it 5.0.1, mdurl 2.0.0, punycode.js 2.3.1, uc.micro 2.1.0.
  • markdown-it is consumed only as the prebuilt UMD bundle (dist/markdown-it.min.js) loaded by the Unity Catalog detail webview (resources/webview-ui/uc-detail.js):
    const md = window.markdownit({html: false, linkify: true, typographer: false});
    md.render(text)
    That constructor + render API is unchanged across v12→v14, and v14 still exposes the window.markdownit UMD global — no call-site changes needed. There's no TypeScript import of markdown-it and no @types/markdown-it dependency.

Verification

  • yarn install regenerates cleanly; every resolved dep verified to exist on public npm (no phantom versions).
  • yarn run build passes; package:copy-markdown-it ships the v14 markdown-it.min.js into out/.
  • Webview usage reviewed against the v14 API (constructor + render + linkify) — compatible.

Backward compatibility: only the bundled markdown renderer version changes; webview API usage is identical. No persisted state, config, or public API change.

Closes #1946.

This pull request and its description were written by Isaac.

*Why*
Dependabot's markdown-it 12->14 PR (#1946) could not merge: its lockfile pinned
`linkify-it@5.0.2`, a version that does not exist on the public npm registry
(latest is 5.0.1), so `yarn install --immutable` failed in CI with a 403 from the
JFrog mirror (nothing to serve). This PR regenerates the lockfile against real,
published versions and takes the markdown-it major upgrade deliberately.

*What*
- Bump `markdown-it` to `^14.2.0` in packages/databricks-vscode/package.json.
- Regenerate yarn.lock; it resolves to real versions: markdown-it 14.2.0 with
  linkify-it 5.0.1, mdurl 2.0.0, punycode.js 2.3.1, uc.micro 2.1.0.
- markdown-it is consumed only as the prebuilt UMD bundle
  (`dist/markdown-it.min.js`) loaded by the Unity Catalog detail webview
  (resources/webview-ui/uc-detail.js): `window.markdownit({html:false,
  linkify:true, typographer:false})` + `md.render(text)`. That constructor +
  render API is unchanged across v12->v14, and v14 still exposes the
  `window.markdownit` UMD global, so no call-site changes are needed. There is
  no TypeScript import of markdown-it and no `@types/markdown-it` dependency.

*Verification*
- `yarn install` regenerates cleanly; all resolved deps verified to exist on
  public npm (no phantom versions).
- `yarn run build` passes; `package:copy-markdown-it` ships the v14
  `markdown-it.min.js` (124 KB) into `out/`.
- Webview usage reviewed against v14 API (constructor + render + linkify) — compatible.

Backward compatibility: only the bundled markdown renderer version changes; the
webview API usage is identical. No persisted state, config, or public API change.

Co-authored-by: Isaac
@rugpanov rugpanov temporarily deployed to test-trigger-is July 2, 2026 14:03 — with GitHub Actions Inactive
@rugpanov

rugpanov commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

Integration tests: https://github.com/databricks-eng/eng-dev-ecosystem/actions/runs/28597288587

Result: 25 passing / 7 failing — matches the current main/e2e baseline. Zero Can't find view control "CONFIGURATION" (activation) failures, and no markdown-it-related failures. The 7 reds are the pre-existing environmental flakes (terraform-registry network, Item "access" not found in the UC tree view, login timeout, ENOENT) that fail identically on main regardless of this change.

@rugpanov rugpanov enabled auto-merge (squash) July 2, 2026 16:35
@rugpanov rugpanov temporarily deployed to test-trigger-is July 2, 2026 16:35 — with GitHub Actions Inactive
@rugpanov rugpanov merged commit 1622807 into main Jul 2, 2026
6 checks passed
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/vscode

Inputs:

  • PR number: 1951
  • Commit SHA: ededeb0932eccf28145d655fbe64304b27b573a9

Checks will be approved automatically on success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants