Repository navigation
fix: bump js-yaml to 4.3.2 (supersedes #266) - #291
Merged
Merged
Conversation
Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 4.3.2. - [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.2/CHANGELOG.md) - [Commits](nodeca/js-yaml@4.3.1...4.3.2) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.3.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
CaseyKelly
marked this pull request as ready for review
September 24, 2026 01:13
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
📦 Next.js Bundle Analysis for fantasyphishThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
🎭 Playwright test results✅ 38 passed, 0 failed, 4 flaky, 1 skipped (43 total)
Full HTML report with traces, screenshots, and console logs: download the |
This branch was successfully deployed
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.
Same one-commit lockfile change as Dependabot's #266 (js-yaml 4.3.1 → 4.3.2, a dev-only transitive dependency; the release backports merge-sequence limits for the CPU-usage issue in nodeca/js-yaml#797).
Why a separate PR
#266 can't go green as-is. GitHub gives Dependabot-triggered workflow runs no Actions secrets, so
NEON_API_KEY/TEST_DATABASE_URL/TEST_DIRECT_URLare empty there. No Neon branch gets created,prisma migrate deployfalls back tolocalhost:5432(P1001), andtest,lint-typecheck-buildandanalyzeall fail. Re-running doesn't help because re-runs keep Dependabot's permissions. This branch isn't pushed by Dependabot, so its runs get the normal secrets.Once this merges, Dependabot should close #266 as superseded.
Verification
npm ci,npm run typecheck,npm run lintpass locallyjs-yamlresolves to 4.3.2🤖 Generated with Claude Code
https://claude.ai/code/session_01FYAwNpBcL88R2Ks8s5GR7X
Generated by Claude Code