Skip to content

chore(deps): bump json gem to 2.21.2 (Dependabot #53) - #37

Merged
comphy-bot merged 2 commits into
mainfrom
rayleigh-cloud/bump-json-gem-6d26
Aug 24, 2026
Merged

chore(deps): bump json gem to 2.21.2 (Dependabot #53)#37
comphy-bot merged 2 commits into
mainfrom
rayleigh-cloud/bump-json-gem-6d26

Conversation

@VatsalSy

@VatsalSy VatsalSy commented Aug 24, 2026

Copy link
Copy Markdown
Member

Description

Security hygiene PR to resolve Dependabot alert #53 for the transitive Ruby json gem in Gemfile.lock.

Also fixes a pre-existing CI failure on main where the npm js-yaml security override (>=4.3.1) resolved to js-yaml 5.x, breaking markdownlint-cli2 ESM imports during npm run lint:md.

Type of Change

  • Bug fix
  • New feature
  • Content update (Team/Publication)
  • Documentation update
  • Other (please describe) — dependency security update

Changes Made

  • Ran bundle update json to bump json from 2.20.02.21.2
  • Pinned npm override js-yaml from >=4.3.1 to 4.3.1 so markdownlint-cli2 keeps a default ESM export (js-yaml 5.x removed it)
  • Updated package-lock.json accordingly
  • json is a transitive dependency via faradayjekyll-gistoctokit; it is not pinned in the Gemfile

Vulnerability

Major-version judgment

Not required. This is a patch-level bump within the 2.x line (2.20.0 → 2.21.2). No Gemfile changes needed.

Testing Done

  • bundle update json completed successfully
  • bundle exec jekyll build succeeds locally
  • npm ci && npm run lint:md passes locally
  • Jekyll site CI passes on this branch
  • Tested locally using bundle exec jekyll serve
  • Checked all links and references
  • Verified content formatting
  • Cross-browser testing (if UI changes)

Related Issues

Addresses Dependabot alert #53.

Checklist

  • Code follows the project's style guidelines
  • Changes have been tested locally (Jekyll build)
  • All links are valid and working
  • Images are optimized and properly sized
  • Content is properly formatted
  • Documentation has been updated (if needed)

Additional Notes

CI (Jekyll site CI) is green on this PR. Do not merge until Dependabot marks alert #53 resolved.

Open in Web Open in Cursor 

Summary by CodeRabbit

  • Chores
    • Updated the YAML parsing package version constraint to use a fixed, specific release.

Address Dependabot alert #53 by updating the transitive json dependency
from 2.20.0 to 2.21.2 via `bundle update json`.

Fixes heap-use-after-free in JSON::ResumableParser (GHSA-9hj4-r449-hfvc).

Co-authored-by: Vatsal Sanjay | CoMPhy Lab <[email protected]>
@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1f17ca60-160a-4327-bb99-4b13b878b4a2

📥 Commits

Reviewing files that changed from the base of the PR and between 8798f0a and bb796cc.

⛔ Files ignored due to path filters (2)
  • Gemfile.lock is excluded by !**/*.lock
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (2)
  • GitHub Check: Cursor Bugbot
  • GitHub Check: build
🔇 Additional comments (1)
package.json (1)

42-42: LGTM!


📝 Walkthrough

Walkthrough

The js-yaml override in package.json now requires exactly version 4.3.1 instead of version 4.3.1 or newer.

Changes

Dependency override

Layer / File(s) Summary
Pin js-yaml version
package.json
The js-yaml override now specifies exactly version 4.3.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to bb796

This PR updates dependencies and reports a successful Jekyll build; no actionable merge-blocking risk remains beyond normal CI checks and confirming the security alert is resolved.

Suggested reviewers: comphy-bot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the dependency update to json gem 2.21.2, which is a primary objective of the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch rayleigh-cloud/bump-json-gem-6d26

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

@VatsalSy
VatsalSy marked this pull request as ready for review August 24, 2026 08:41
@VatsalSy
VatsalSy requested a lite review from Copilot August 24, 2026 08:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

The npm override `js-yaml: >=4.3.1` resolved to js-yaml 5.x, which
removed the default export that markdownlint-cli2 expects. Pin to 4.3.1
to keep security fixes while restoring `npm run lint:md` in CI.

Co-authored-by: Vatsal Sanjay | CoMPhy Lab <[email protected]>
@comphy-bot
comphy-bot merged commit 626dba9 into main Aug 24, 2026
4 checks passed
@VatsalSy
VatsalSy deleted the rayleigh-cloud/bump-json-gem-6d26 branch August 24, 2026 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants