chore: refresh bun.lock after mermaid 11.15.0 update#905
Merged
Conversation
Dependabot обновил mermaid в package.json в #899, но bun.lock не был обновлён — следствие: `bun install --frozen-lockfile` в CI падает с 'lockfile had changes, but lockfile is frozen'. Lockfile синхронизирован локальным `bun install`. Никаких других изменений.
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
2 participants
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.
Проблема
После мержа dependabot-PR #899 (
mermaid11.14.0 → 11.15.0) обновилсяpackage.jsonиpnpm-lock.yaml, но неbun.lock. Это блокирует CI всех последующих PR — командаbun install --frozen-lockfileпадает с:```
error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile
```
Решение
Локально запустил
bun installбез--frozen-lockfile— bun обновилbun.lockпод актуальныйpackage.json. Никаких других изменений (толькоbun.lock).Эффект
После мержа этого PR все ранее открытые / новые PR в Docs смогут пройти CI. В частности, разблокируется PR #902 (sync для MS3 1.11.0-beta1).
Долгосрочно
Dependabot в этом репо настроен на обновление
pnpm-lock.yaml, но неbun.lock. При следующем обновлении npm-зависимости проблема повторится. Стоит донастроить dependabot или CI:bun installбез--frozen-lockfile(но это ослабляет гарантии воспроизводимости).bun.lockпосле dependabot-обновлений.Отдельной задачей, не в этом PR.