Repository navigation
chore: commit lockfile and set up Dependabot - #487
Merged
Merged
Conversation
This library previously committed no lockfile (.yarnrc forced --no-lockfile and yarn.lock was gitignored). Without a lockfile, Dependabot builds its npm graph from package.json alone and is blind to transitive dependencies, so its security and version updates only ever cover direct deps. A committed lockfile does not ship to consumers (yarn.lock is excluded from the npm tarball), so this only affects local and CI installs and restores full dependency visibility. - Remove .yarnrc no-lockfile directives and un-ignore yarn.lock - Commit yarn.lock - Add .github/dependabot.yml (npm at /, github-actions; @hubspot/* grouped separately, 7-day cooldown on each entry) - Add a daily fresh-install-check workflow that does a clean install from package.json then build + test, as a smoke test for upstream breakage that a fresh consumer install would hit. It never commits or opens a PR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The CLI's fresh-install check already resolves this library's runtime deps floating, as a real consumer install does. For the library itself the committed lockfile, normal CI, and Dependabot (which re-runs full CI on each bump) provide adequate coverage, so a separate daily check here is redundant. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Major versions are breaking and cannot be merged without additional work, so they should not arrive as routine dependency PRs. Ignore semver-major for all version updates across every ecosystem. This does not affect security updates, which are exempt from update-types ignores, so Dependabot can still propose a major bump when it is required to fix a vulnerability. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
camden11
marked this pull request as ready for review
September 16, 2026 19:10
camden11
requested review from
ashleighliu,
brandenrodgers and
joe-yeager
as code owners
September 16, 2026 19:10
joe-yeager
approved these changes
Sep 16, 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.
This library previously committed no lockfile (.yarnrc forced --no-lockfile and yarn.lock was gitignored). Without a lockfile, Dependabot builds its npm graph from package.json alone and is blind to transitive dependencies, so its security and version updates only ever cover direct deps. A committed lockfile does not ship to consumers (yarn.lock is excluded from the npm tarball), so this only affects local and CI installs and restores full dependency visibility.
Description and Context
Pre-review checklist
/ldl:code-checkskill has been run and the feedback has been addressedScreenshots
TODO
Who to Notify