chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1 by ashleyshaw · Pull Request #1047 · lightspeedwp/.github

ashleyshaw · 2026-07-15T19:57:38Z

Chore Pull Request

Linked issues

Relates to #1036 (superseded — closed; this is a clean re-creation from current develop with the code fix applied).

Summary

Bumps js-yaml from 4.2.0 to 5.2.1 (major version). js-yaml 5.x dropped its default export — it only ships named ESM exports now (load, dump, etc.). This broke every file using import yaml from "js-yaml" with The requested module 'js-yaml' does not provide an export named 'default'.

Changes

package.json / package-lock.json: js-yaml 4.2.0 → 5.2.1.
15 files switched from a default import to a namespace import (import * as yaml from "js-yaml" / import * as YAML from "js-yaml"), which resolves the same way in both v4 and v5 since load/dump were always named exports. All 15 files only ever call .load(...).
No changes needed for the ~27 files that use require("js-yaml") — js-yaml's CJS build still exports plain exports.load = ... properties, so CommonJS require was never affected by the default-export removal.

Impact / Compatibility

Runtime/behaviour changes: None — .load() behaves identically; only the import syntax changed.
Build/dev-experience impact: None.

Verification

CI passes
Local build and smoke tests
Docs updated if developer-facing

Risk & Rollback

Risk level: Low
Rollback plan: revert commit.

Changelog

Fixed

Fixed js-yaml 5.x compatibility — 15 files using import yaml from "js-yaml" broke on the removed default export; switched to namespace imports.

Changed

Bumped js-yaml 4.2.0 → 5.2.1.

Checklist (Global DoD / PR)

🤖 Generated with Claude Code

js-yaml 5.x dropped its default export (it only ships named ESM exports now: load, dump, etc. — no `export default`). This broke every file using `import yaml from "js-yaml"` with "The requested module 'js-yaml' does not provide an export named 'default'". Fixes all 15 affected files by switching to a namespace import (`import * as yaml from "js-yaml"`), which resolves the same way in both v4 and v5 since `load`/`dump` were always named exports. CJS `require("js-yaml")` call sites are unaffected — js-yaml's CJS build still exports plain `exports.load = ...` properties, so there's no default-export dependency there. Verified: npm ci, npm run lint:js (0 errors), npm run test:js (668/668 passing, including the check-template-labels.js suite that was the original blocker for this bump).

coderabbitai · 2026-07-15T19:57:47Z

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: cfe054bf-eb5f-45c7-9df7-859e0a6abfda

📥 Commits

Reviewing files that changed from the base of the PR and between 5bf7976 and e7f9dd7.

⛔ Files ignored due to path filters (1)

package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (17)

.github/metrics/frontmatter-metrics.js
.github/scripts/validate-footers.js
CHANGELOG.md
package.json
scripts/agents/branding-unified.agent.js
scripts/agents/branding.agent.js
scripts/agents/includes/badges.js
scripts/agents/includes/check-template-labels.js
scripts/agents/includes/header-footer.js
scripts/agents/includes/label-lookup.js
scripts/agents/includes/label-sync.js
scripts/agents/includes/labeler-utils.js
scripts/agents/labeling.agent.js
scripts/agents/meta.agent.js
scripts/audit-branding-patterns.js
scripts/remediation-wave-4f.js
scripts/validation/validate-agents.js

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch chore/js-yaml-5-migration

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-07-15T19:57:47Z

✅ Template check passed after update. Thanks for fixing the PR description.

gemini-code-assist

Code Review

This pull request upgrades the js-yaml dependency from version ^4.2.0 to ^5.2.1 in package.json and package-lock.json. To accommodate this upgrade, the import statements for js-yaml have been updated from default imports to namespace imports (import * as yaml from "js-yaml") across various scripts and GitHub Action utilities. There are no review comments, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

github-actions · 2026-07-15T19:58:27Z

🔍 Reviewer Summary for PR #1047

CI Status: ✅ success
Files changed: 18
Risk Distribution: 0 critical, 3 high, 0 medium, 15 low

Recommendations

Ready to proceed pending human review

github-actions · 2026-07-15T20:00:04Z

Metadata governance

Item: chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1 #1047
Assignee: ashleyshaw
Milestone: none
Linked issues/PRs: chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1 #1036

ashleyshaw mentioned this pull request Jul 15, 2026

chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1 #1036

Closed

github-actions Bot assigned ashleyshaw Jul 15, 2026

github-actions Bot added status:needs-review Awaiting code review type:chore Chore / small hygiene change priority:normal Default priority area:labels Label governance and routing area:dependencies Composer/npm dependency work area:scripts Scripts & tooling labels Jul 15, 2026

gemini-code-assist Bot reviewed Jul 15, 2026

View reviewed changes

github-actions Bot added lang:js JavaScript/TypeScript lang:json JSON config/content meta:needs-changelog Requires a changelog entry before merge labels Jul 15, 2026

docs: add changelog entry for js-yaml 5 migration (#1047)

66bb678

github-actions Bot added area:documentation Docs & guides lang:md Markdown content/docs labels Jul 15, 2026

ashleyshaw added 2 commits July 15, 2026 22:09

chore: merge develop into js-yaml-5 branch, resolve changelog conflict

037aa5a

chore: merge develop into js-yaml-5 branch, resolve eslint-10 conflicts

e7f9dd7

ashleyshaw merged commit 51c1cf6 into develop Jul 15, 2026
27 checks passed

ashleyshaw deleted the chore/js-yaml-5-migration branch July 15, 2026 20:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1#1047

chore(deps-dev): bump js-yaml from 4.2.0 to 5.2.1#1047
ashleyshaw merged 4 commits into
developfrom
chore/js-yaml-5-migration

ashleyshaw commented Jul 15, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

Review limit reached

Uh oh!

github-actions Bot commented Jul 15, 2026 •

edited

Loading

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

github-actions Bot commented Jul 15, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

ashleyshaw commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Chore Pull Request

Linked issues

Summary

Changes

Impact / Compatibility

Verification

Risk & Rollback

Changelog

Fixed

Changed

Checklist (Global DoD / PR)

Uh oh!

coderabbitai Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

github-actions Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

github-actions Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Reviewer Summary for PR #1047

Recommendations

Uh oh!

github-actions Bot commented Jul 15, 2026

Metadata governance

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

ashleyshaw commented Jul 15, 2026 •

edited

Loading

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

github-actions Bot commented Jul 15, 2026 •

edited

Loading

github-actions Bot commented Jul 15, 2026 •

edited

Loading