Repository navigation
chore(deps): SUP-4155 Refresh GitHub dependency inventory - #159
Merged
Merged
Conversation
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.


GitHub still reports dependency files last checked on 9 October 2026, before the SUP-4142 dependency fixes merged on 20 October. This temporary commit changes lockfile whitespace to try to trigger fresh dependency graph processing when merged into
master, so we can distinguish stale alerts from vulnerabilities that still need fixes.Dependency data is unchanged: each lockfile gains one blank line, JSON locks parse identically, and
git diff --ignore-blank-linesreports no content changes. No dependency installation or application tests are needed for this whitespace-only change. Existing CI runs where configured; there is no new workflow.After merge, verify the dependency-file check timestamp and SBOM versions against the merged locks. The commit can then be reverted without undoing the dependency upgrades. Recent Actions outages are a possible contributor, but the indexing failure's cause is unconfirmed.
Tracked together with the other nine repositories in SUP-4155. Keep that ticket open until the refresh has been verified across all ten.