Repository navigation
[GIT-84] Refresh dependencies - #85
Open
itsryanarmani wants to merge 1 commit into
Open
itsryanarmani wants to merge 1 commit into
itsryanarmani wants to merge 1 commit into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
![pooriaarab-grokbot[bot]](https://avatars.githubusercontent.com/u/42897904?s=60&v=4){kind=small}
There was a problem hiding this comment.
Not merging yet: the CI build job fails before running anything (checkout of the private repo via the SSH deploy key returns 'Repository not found', same on main and every other open PR), so the several runtime majors here (firebase 13, firebase-admin 14, mermaid 12, diff 9, vinext beta->1.4, typescript 6) have no CI build signal. Once the deploy key/secret is fixed, rerun build and this can go.
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.
Closes #84
What
Refresh every direct dependency to its latest published release across the root package and the promo-video app, and regenerate both package-lock files with npm.
held back:
Why
Cut dependency drift by moving to the latest versions while keeping the verified builds and lockfiles consistent, so dependabot and future feature work build on current releases.
How I verified
npm run build:vinext -> build complete
npx tsc --noEmit -> passed
bunx oxlint -> passed
The root and promo-video lockfiles resolve the held versions.
Proof: n/a - dependency-only change, no visible output change.
Review
Reviewed-by: claude-hub:claude-sonnet-5-5
Verdict: 0 major
Assisted-by: pi:deepseek-v4-flash-0731