Skip to content

fix(deps): update dependency slate-react to ^0.123.0#9764

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/slate-react-0.x
Open

fix(deps): update dependency slate-react to ^0.123.0#9764
renovate[bot] wants to merge 1 commit intomainfrom
renovate/slate-react-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jan 19, 2026

This PR contains the following updates:

Package Change Age Confidence
slate-react ^0.120.0^0.123.0 age confidence

Release Notes

ianstormtaylor/slate (slate-react)

v0.123.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 7am on Tuesday,before 7am on Wednesday" in timezone Australia/Sydney, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/slate-react-0.x branch from 001372a to 88a76af Compare February 2, 2026 14:53
@renovate renovate bot force-pushed the renovate/slate-react-0.x branch from 88a76af to 31aa0c0 Compare February 16, 2026 16:58
@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: React Router has Path Traversal in File Session Storage in npm @remix-run/node

CVE: GHSA-9583-h5hc-x8cw React Router has Path Traversal in File Session Storage (CRITICAL)

Affected versions: < 2.17.2

Patched version: 2.17.2

From: examples/framework-remix/package.jsonnpm/@remix-run/node@1.19.3

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@remix-run/node@1.19.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @remix-run/dev is 98.0% likely obfuscated

Confidence: 0.98

Location: Package overview

From: examples/framework-remix/package.jsonnpm/@remix-run/dev@1.19.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@remix-run/dev@1.19.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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.

0 participants