Skip to content

[Snyk] Upgrade @swc/core from 1.3.68 to 1.15.10#12153

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-upgrade-cb5b337db545024dbea1df8f4ee3077d
Closed

[Snyk] Upgrade @swc/core from 1.3.68 to 1.15.10#12153
q1blue wants to merge 1 commit intomasterfrom
snyk-upgrade-cb5b337db545024dbea1df8f4ee3077d

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to upgrade @swc/core from 1.3.68 to 1.15.10.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 484 versions ahead of your current version.

  • The recommended version was released 25 days ago.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:


EntelligenceAI PR Summary

This PR upgrades the SWC compiler toolchain in the Storybook package from version 1.3.x to 1.15.x.

  • Updated @swc/core dependency specification in package.json from ^1.3.46 to ^1.15.10
  • Resolved @swc/core version in yarn.lock updated from 1.3.68 to 1.15.11
  • Added new dependencies: @swc/counter@^0.1.3 and @swc/types@^0.1.25
  • Relaxed @swc/helpers peer dependency constraint from ^0.5.0 to >=0.5.17
  • Updated all platform-specific binaries (darwin, linux, win32) and architectures (arm64, x64, ia32, arm) with new checksums

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the upgrade of the @swc/core dependency within the Storybook project. The update aims to keep the project's dependencies current, leveraging the latest features, performance enhancements, and security improvements offered by the newer version of @swc/core. The changes primarily involve updating the package version in package.json and synchronizing the yarn.lock file to reflect the new dependency tree and checksums.

Highlights

  • Dependency Upgrade: The @swc/core dependency has been upgraded from version 1.3.68 to 1.15.10 in storybook/package.json.
  • Lock File Updates: The storybook/yarn.lock file has been updated to reflect the new @swc/core version, including its platform-specific packages (e.g., @swc/core-darwin-arm64, @swc/core-linux-x64-gnu), which are now at version 1.15.11.
  • New Transitive Dependencies: As part of the @swc/core upgrade, new transitive dependencies @swc/counter and @swc/types have been introduced and recorded in storybook/yarn.lock.
  • Peer Dependency Adjustment: The peer dependency requirement for @swc/helpers within storybook/yarn.lock has been updated to >=0.5.17.
Changelog
  • storybook/package.json
    • Updated @swc/core dependency from ^1.3.46 to ^1.15.10.
  • storybook/yarn.lock
    • Updated all platform-specific @swc/core packages (e.g., @swc/core-darwin-arm64, @swc/core-linux-x64-gnu) from version 1.3.68 to 1.15.11.
    • Updated the main @swc/core entry from version 1.3.68 to 1.15.11.
    • Added new dependencies @swc/counter and @swc/types under the @swc/core entry.
    • Adjusted the peer dependency for @swc/helpers from ^0.5.0 to >=0.5.17.
    • Updated checksums for @swc/core and typescript entries.
Activity
  • This pull request was automatically created by Snyk to upgrade the @swc/core dependency.
  • Snyk noted that the recommended version is 484 versions ahead of the current one and was released 25 days ago.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@socket-security
Copy link
Copy Markdown

@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 High
License policy violation: npm bcrypt-pbkdf under BSD-3-Clause-HP

License: BSD-3-Clause-HP - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/cypress@10.11.0npm/bcrypt-pbkdf@1.0.2

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/bcrypt-pbkdf@1.0.2. 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
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.8.4. 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
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: cypress/package.jsonnpm/typescript@4.9.5

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.9.5. 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

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR upgrades the SWC compiler toolchain in the Storybook package from version 1.3.x to 1.15.x, representing a significant minor version jump. The update affects both the package.json dependency declaration and the yarn.lock file, which reflects the actual resolved versions and their platform-specific binaries. The upgrade introduces two new dependencies (@swc/counter and @swc/types) and relaxes the peer dependency constraint for @swc/helpers. All platform-specific binaries (darwin, linux, win32) across different architectures (arm64, x64, ia32, arm) are updated with new checksums. This modernization brings potential performance improvements, bug fixes, and new features from multiple intermediate SWC releases.

Changes

File(s) Summary
storybook/package.json Updated @swc/core dependency from ^1.3.46 to ^1.15.10, a significant minor version bump for the SWC compiler.
storybook/yarn.lock Updated @swc/core and all platform-specific binaries from version 1.3.68 to 1.15.11; added two new dependencies (@swc/counter@^0.1.3 and @swc/types@^0.1.25); relaxed @swc/helpers peer dependency from exactly ^0.5.0 to >=0.5.17; updated checksums for all platform targets and architectures.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant App as Storybook Application
    participant SWC as @swc/core (v1.15.11)
    participant Counter as @swc/counter
    participant Types as @swc/types
    participant Binary as Platform Binary
    participant Helpers as @swc/helpers (peer)

    Note over App,Helpers: Dependency Update: @swc/core 1.3.46 → 1.15.10

    App->>SWC: Install/Update dependency
    activate SWC
    
    SWC->>Counter: Require @swc/counter (^0.1.3)
    activate Counter
    Counter-->>SWC: Provide counter utilities
    deactivate Counter
    
    SWC->>Types: Require @swc/types (^0.1.25)
    activate Types
    Types->>Counter: Require @swc/counter
    activate Counter
    Counter-->>Types: Provide counter utilities
    deactivate Counter
    Types-->>SWC: Provide type definitions
    deactivate Types
    
    SWC->>Binary: Load platform-specific binary<br/>(darwin-arm64, linux-x64, win32-x64, etc.)
    activate Binary
    Binary-->>SWC: Native compilation capabilities
    deactivate Binary
    
    opt Peer Dependency Available
        App->>Helpers: Optionally provide @swc/helpers (>=0.5.17)
        Helpers-->>SWC: Runtime helper functions
    end
    
    SWC-->>App: Ready for transpilation
    deactivate SWC
    
    Note over App,Helpers: New dependencies: @swc/counter, @swc/types<br/>Updated peer dependency constraint
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This PR upgrades @swc/core in the storybook package. I've raised a high-severity concern regarding the significant version jump, which increases the risk of breaking changes. I also pointed out that this change introduces a version inconsistency for @swc/core across packages in the monorepo, which is a maintainability concern. Please see the detailed comment in storybook/package.json.

Comment thread storybook/package.json
},
"dependencies": {
"@swc/core": "^1.3.46",
"@swc/core": "^1.15.10",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

This is a very large version jump for @swc/core (from 1.3.x to 1.15.x), which carries a high risk of breaking changes that could affect the Storybook build, despite Snyk's metadata indicating otherwise.

Additionally, this update creates a version inconsistency for @swc/core within the monorepo, as the packages/cli package remains on an older version (^1.3.46). For better maintainability, it's recommended to align dependency versions across the monorepo. Consider upgrading @swc/core and its related packages (like @swc/helpers) in packages/cli as well, either in this PR or a follow-up.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants