chore: remove example/fixture lockfiles from git to reduce Dependabot noise#8334
Merged
thatmichael85 merged 1 commit intomainfrom Apr 11, 2026
Merged
Conversation
… noise Dependabot generates alerts against this repo for transitive dependencies in standalone example apps and integration test fixtures — directories explicitly excluded from the pnpm workspace. None of these alerts affect shipped library code. Changes: - Remove 20 pnpm-lock.yaml files from git tracking (18 examples + 2 integration test fixtures) - Add .gitignore rules so they stay untracked going forward - Add .github/dependabot.yml to configure Dependabot version updates for the root workspace only, with GitHub Actions updates monthly What this does NOT break: - update-examples.mjs: regenerates lockfiles locally via pnpm --ignore-workspace --no-frozen-lockfile i (never reads from git) - Integration tests: use npm install --no-save with local tgz files - Post-release workflow: git-auto-commit-action respects .gitignore - Users cloning examples: pnpm install resolves from pinned versions
thatmichael85
requested review from
acywatson,
etrepum,
fantactuka,
ivailop7,
potatowagon,
takuyakanbr and
zurfyx
as code owners
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
etrepum
approved these changes
Apr 11, 2026
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.
Summary
Dependabot currently reports 83 open security alerts against this repo. After investigation, none affect shipped library code — they all come from transitive dependencies in:
examples/*/pnpm-lock.yaml(18 standalone example apps)scripts/__tests__/integration/fixtures/*/pnpm-lock.yaml(2 test fixtures)pnpm-lock.yaml(dev/build tooling)This PR addresses the first two categories by removing those lockfiles from git tracking.
Changes
pnpm-lock.yamlfiles from git (18 examples + 2 integration test fixtures).gitignorerules so they stay untracked going forward.github/dependabot.ymlto configure Dependabot version updates for the root workspace only, with GitHub Actions updates on a monthly cadenceWhat this does NOT break
update-examples.mjs(post-release)pnpm --ignore-workspace --no-frozen-lockfile i. Never reads existing lockfiles from git.npm install --no-save <tgz>with freshly-built packages. Lockfiles are never referenced.call-post-release.yml)git-auto-commit-actionwhich respects.gitignore. Updatedpackage.jsonfiles are still committed; lockfiles are simply skipped.pnpm installresolves fresh deps from the pinned versions inpackage.json. Direct deps (lexical,@lexical/react, etc.) are pinned to exact versions.Context
These directories are explicitly excluded from the pnpm workspace (
pnpm-workspace.yaml):The lockfiles existed for convenience but were generating a steady stream of Dependabot alerts (vite, picomatch, lodash, undici, dompurify, node-forge, etc.) that appeared as security issues against the main project despite having zero impact on shipped packages.
Expected impact
This should eliminate ~39 of the 83 current Dependabot alerts (those sourced from example and fixture lockfiles). The remaining ~44 alerts from the root
pnpm-lock.yamlare legitimate (though still only dev dependencies) and can be addressed separately.