chore(deps): bump mermaid from 11.16.0 to 11.16.1 in /tools/mermaid - #13
Open
dependabot[bot] wants to merge 1 commit into
Open
chore(deps): bump mermaid from 11.16.0 to 11.16.1 in /tools/mermaid#13dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [mermaid](https://github.com/mermaid-js/mermaid) from 11.16.0 to 11.16.1. - [Release notes](https://github.com/mermaid-js/mermaid/releases) - [Commits](https://github.com/mermaid-js/mermaid/compare/mermaid@11.16.0...mermaid@11.16.1) --- updated-dependencies: - dependency-name: mermaid dependency-version: 11.16.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
yeasy
added a commit
that referenced
this pull request
Aug 25, 2026
供应链测试把 action 的 **SHA 按字面钉死**：
self.assertIn("actions/attest-build-provenance@0f67c3f... # v4.1.1", ...)
Dependabot 升级这个 action 时改的正是被断言的那一行，于是断言必然失败、`build` 红、
PR `mergeStateStatus=BLOCKED`。这是**结构性死锁**：该 action 的任何一次升级都会打挂
钉死它的测试，PR 永远合不进来。**全集群 7 个仓库钉的是同一个 SHA，6 个 PR 同时卡在这里**
（agentic #13、aifbs #8、ai_security #17、blockchain #176、ceg #16、docker_practice #578）。
反证很干净：另外 4 个断言写成 `assertIn("actions/attest-build-provenance@")` 的仓库
（claude_guide / peg / fde / llm_internals）**同一个升级早就合进去了**。
断言真正要守的是「release job 必须用 SHA 钉住这个 action」——**这个意图不需要记住是哪个
SHA**。改为 `assertRegex(..., r"actions/attest-build-provenance@[0-9a-f]{40} # v\d")`：
仍然强制 40 位 SHA + `# vN` 溯源注释，**比那 4 个仓库现用的宽松写法更严**，但升级不再撞墙。
同批把 aifbs / ai_security 里 `dependabot/fetch-metadata@25dd0e3... # v3.1.0` 的同款钉死
一并改掉（未升级该 action，只解除钉死）。
同时在主干上直接升掉 Dependabot 提的两个版本，**SHA 逐个用 GitHub API 解引用核过**
（`browser-actions/setup-chrome` 的 tag 是 annotated tag，要走 `git/tags` 再取
`.object.sha`，直接读 `git/ref/tags` 会拿到 tag 对象的 SHA 而误判）：
- `actions/attest-build-provenance` 0f67c3f… v4.1.1 → 4d10147… v4.2.2
- `browser-actions/setup-chrome` 2e1d749… v2.1.2 → 48ad923… v2.2.0（blockchain_guide 已在 2.2.0）
**负向验证**（AGENTS.md 核心约定 4，逐条证明新断言没被改成永真）：把 pin 换成浮动 tag
`@v4` → FAIL；保留 SHA 但删掉 `# vN` 注释 → FAIL；还原 → OK。七个仓库各跑一遍，
结果一致。而「换一个合法 SHA 应当通过」这一条由本提交自身证明——pin 从 v4.1.1 换到
v4.2.2，测试全绿。
各仓库 `check_project_rules`、`unittest discover -s tests -p 'test_*.py'`、
`git diff --check` 均通过；docker_practice 另跑 `npm test` 通过。
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
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.
Bumps mermaid from 11.16.0 to 11.16.1.
Release notes
Sourced from mermaid's releases.
Commits
7ecca0cVersion Packages (#8023)95b1b9cdocs: changemermaidAPI.setConfig()changeset (#8024)acc69f1Merge pull request #8022 from mermaid-js/release/11.16.1eba7287docs: point changesets to correct commit hashes12d472cMerge commit from fork2cd6dcfMerge commit from fork630aa7eMerge commit from fork59b22faMerge commit from fork99af3fcMerge commit from fork2337f7eMerge branch 'test/improve-example.html' into release/11.16.1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.