Skip to content

chore(deps): bump mermaid from 11.16.0 to 11.16.1 in /public/visimer (#3347) - #26

Merged
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync
Aug 11, 2026
Merged

chore(deps): bump mermaid from 11.16.0 to 11.16.1 in /public/visimer (#3347)#26
inkeep-oss-sync[bot] merged 1 commit into
mainfrom
copybara/sync

Conversation

@inkeep-oss-sync

Copy link
Copy Markdown

Copybara-translated 1 Inkeep OSS change. Rebase-merge this PR so the prepared commit lands directly on public main.

…(#3347)

Rebuilt the branch on current main to clear a merge conflict.

public/visimer is a standalone pnpm root and is not a member of the root
pnpm-workspace.yaml, so a mermaid bump there cannot affect the monorepo root
lockfile. Dependabot regenerated /pnpm-lock.yaml anyway as part of the bump.
Because the root lockfile carries floating specifiers and registry sensitive
resolutions, that regeneration reverted unrelated packages back to whatever
main held when the branch was cut, for example @opentelemetry/api 1.9.1 back
to 1.9.0 and @opentelemetry/core 2.6.1 back to 2.5.1. That stale revert was
the entire source of the conflict, not the mermaid bump itself.

The branch now carries only the three visimer app manifests plus visimer's own
pnpm-lock.yaml. The root lockfile is left byte identical to main.

Verified before push:
- git diff origin/main -- pnpm-lock.yaml is empty, and the root lockfile md5
  is unchanged from main
- the visimer lockfile diff is 13 insertions and 13 deletions, limited to
  mermaid 11.16.0 to 11.16.1 and the mermaid-zenuml peer re-peg
- mermaid 11.16.1 declares dependencies identical to 11.16.0 on npm, so no
  transitive churn is expected or present
- pnpm --dir public/visimer install --frozen-lockfile exits 0

GitOrigin-RevId: 43dba5359a9e9b989068a2380a3a6f756a188b96
@inkeep-oss-sync
inkeep-oss-sync Bot merged commit 06b0cbf into main Aug 11, 2026
@inkeep-oss-sync
inkeep-oss-sync Bot deleted the copybara/sync branch August 11, 2026 02:39
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.

0 participants