Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update sentry-javascript monorepo to v7.111.0 #1898

Merged
merged 1 commit into from
Apr 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/node (source) 7.110.1 -> 7.111.0 age adoption passing confidence
@sentry/profiling-node (source) 7.110.1 -> 7.111.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/node)

v7.111.0

Compare Source

  • feat(core): Add server.address to browser http.client spans (#​11663)
  • fix: Ensure next & sveltekit correctly handle browserTracingIntegration (#​11647)
  • fix(browser): Don't assume window.document is available (#​11598)

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 80.71 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 71.68 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped) 75.7 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 65.31 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 35.62 KB
@​sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped) 35.5 KB
@​sentry/browser (incl. Feedback) - Webpack (gzipped) 31.57 KB
@​sentry/browser (incl. sendFeedback) - Webpack (gzipped) 31.58 KB
@​sentry/browser - Webpack (gzipped) 22.78 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 78.89 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 70.25 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 36.02 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 25.27 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 221.21 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 109.01 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 75.79 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 39.3 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 72.17 KB
@​sentry/react - Webpack (gzipped) 22.81 KB
@​sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 90 KB
@​sentry/nextjs Client - Webpack (gzipped) 54.15 KB
@​sentry-internal/feedback - Webpack (gzipped) 17.32 KB

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

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


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (squash) April 18, 2024 18:32
Copy link

coderabbitai bot commented Apr 18, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: npm/@sentry/node@7.110.1, npm/@sentry/profiling-node@7.110.1

View full report↗︎

Copy link

sonarcloud bot commented Apr 18, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

deepsource-io bot commented Apr 18, 2024

Here's the code health analysis summary for commits 006f1af..1536b90. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The code changes involve updating the version of Sentry used in both the package.json and the pnpm-lock.yaml files. It is a minor change and generally does not seem to have an issue at first glance. However, testing should be performed to ensure compatibility and that Sentry’s update did not introduce breaking changes.

@@ -26,8 +26,8 @@
},
"devDependencies": {
"@eslint/js": "^9.0.0",
"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

You're updating the version of @sentry/node package. Please ensure the new version introduces no breaking changes.

"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
"@sentry/profiling-node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

You're updating the version of @sentry/profiling-node. It would be prudent to verify that this new version does not introduce any breaking changes.

@@ -49,11 +49,11 @@ importers:
specifier: ^9.0.0
version: 9.0.0
'@sentry/node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

@sentry/node's version updated; it's wise to ensure compatibility with current codebase and that no deprecated functions are in use.

'@sentry/profiling-node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

The @sentry/profiling-node version has been updated. Make sure to check for any breaking changes introduced in this version.

@@ -1113,13 +1113,13 @@ packages:
Copy link

Choose a reason for hiding this comment

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

The integrity of @sentry-internal/tracing@7.111.0 package has changed. Ensure the change has not introduced any breaking modifications.

@@ -1248,17 +1248,17 @@ packages:
Copy link

Choose a reason for hiding this comment

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

Verify @sentry/node's new integrity value; it reflects the change and could potentially introduce breaking changes.

'@sentry/types': 7.110.1
'@sentry/utils': 7.110.1
'@sentry-internal/tracing': 7.111.0
'@sentry/core': 7.111.0
Copy link

Choose a reason for hiding this comment

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

The resolution integrity of @sentry/profiling-node@7.111.0 package has been updated. It is advisable to check for any breaking changes introduced by this version.

/@sentry/profiling-node@7.110.1:
resolution: {integrity: sha512-htqOzb/IPyC27LSAhWy/9J1fqNZNPhgDSXxPyHNo4aWHPpimDIEClues04KGWNNXH2GRe5ttwavX2PHUQG+dwQ==}
/@sentry/profiling-node@7.111.0:
resolution: {integrity: sha512-xJCi2EBf0rQ68kSuQHdKpLDOTjQJUtFGHn0QlaVacchgZZaTiDfJKD5dQhuBJZaul5Nrjq8OOFzwRo2/G8uVIA==}
engines: {node: '>=8.0.0'}
hasBin: true
requiresBuild: true
Copy link

Choose a reason for hiding this comment

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

Updated @sentry/types version. Check for compatibility and deprecated functions after update.

@@ -1267,15 +1267,15 @@ packages:
node-abi: 3.56.0
dev: true

/@sentry/types@7.110.1:
resolution: {integrity: sha512-sZxOpM5gfyxvJeWVvNpHnxERTnlqcozjqNcIv29SZ6wonlkekmxDyJ3uCuPv85VO54WLyA4uzskPKnNFHacI8A==}
Copy link

Choose a reason for hiding this comment

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

Be aware of the new integrity value for '@sentry/utils'. If this package is critical to your application, comprehensive testing is recommended.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The changes are primarily updates to the version of '@sentry' dependencies across various files. It's good to stay up-to-date with the latest versions to get bug fixes and other improvements, but it's also important to be sure that these updates don't introduce any breaking changes. No function, methods or core coding changes are present in the pull request.

@@ -26,8 +26,8 @@
},
"devDependencies": {
"@eslint/js": "^9.0.0",
"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

The '@sentry/node' package has been updated from version '7.110.1' to '7.111.0. Please ensure that this doesn't break any existing functionality, especially error reporting and event capturing.

"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
"@sentry/profiling-node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

The '@sentry/profiling-node' package has been updated from version '7.110.1' to '7.111.0'. Check if this update includes new profiling features or changes that may impact current usage.

@@ -49,11 +49,11 @@ importers:
specifier: ^9.0.0
version: 9.0.0
'@sentry/node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

The '@sentry/node' package version has also been updated in the pnpm-lock.yaml file. It's good that package.json and pnpm-lock.yaml files are in sync.

specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
version: 7.111.0
Copy link

Choose a reason for hiding this comment

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

The '@sentry/profiling-node' package version update is also reflected in the pnpm-lock.yaml file. Consistency is maintained between package.json and pnpm-lock.yaml files.

/@sentry/node@7.110.1:
resolution: {integrity: sha512-n6sNzZJ/ChfyCI1FxuGWgloeevC8j2vax3vXM4IZrSIm5hS1d9L2oCJ4HEPuxGUxCkQ1f4kXPcdmNaQsWH0JBw==}
/@sentry/node@7.111.0:
resolution: {integrity: sha512-bTLZNETT7W89HEk04rwsch02KSpu++Yec/BEyM3AxUNY+ZQ9ZLL/lrNZuCwbe7fURpKoZrvGAhxpPjgs5UcB9w==}
engines: {node: '>=8'}
dependencies:
Copy link

Choose a reason for hiding this comment

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

Dependencies of '@sentry/node' are also updated to the new version '7.111.0'. This is expected as all are part of the '@sentry' package.

'@sentry/utils': 7.110.1
'@sentry-internal/tracing': 7.111.0
'@sentry/core': 7.111.0
'@sentry/types': 7.111.0
Copy link

Choose a reason for hiding this comment

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

The '@sentry/profiling-node' integrity line has changed, signifying a new download was made due to the version change. Make sure this doesn't impact any current profiling workflow.

@@ -1267,15 +1267,15 @@ packages:
Copy link

Choose a reason for hiding this comment

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

The '@sentry/types' package's integrity hash has been updated due to the new version '7.111.0'. Make sure this doesn't alter any type definitions that are currently being used.

@@ -1267,15 +1267,15 @@ packages:
node-abi: 3.56.0
dev: true

/@sentry/types@7.110.1:
resolution: {integrity: sha512-sZxOpM5gfyxvJeWVvNpHnxERTnlqcozjqNcIv29SZ6wonlkekmxDyJ3uCuPv85VO54WLyA4uzskPKnNFHacI8A==}
/@sentry/types@7.111.0:
Copy link

Choose a reason for hiding this comment

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

The '@sentry/utils' package's new version '7.111.0' has changed its integrity hash. Please check if utility functions and helpers still work in the same way.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

This review summarizes the changes made on the '@sentry' packages from version 7.110.1 to 7.111.0 in both the package.json and pnpm-lock.yaml files. From the diff, we can see that the new updates have been reflected correctly across all dependencies. However, please ensure that the updated packages are tested thoroughly for compatibility issues with the current system before these changes are merged into the main branch.

@@ -26,8 +26,8 @@
},
"devDependencies": {
"@eslint/js": "^9.0.0",
"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

The '@sentry/node' package has been updated to version 7.111.0. Double check for any breaking changes in the new version and test thoroughly before merging.

"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
"@sentry/profiling-node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

The '@sentry/profiling-node' package has been updated to version 7.111.0. This might affect profiling in the application. Validate the profiling after upgrading.

@@ -49,11 +49,11 @@ importers:
specifier: ^9.0.0
version: 9.0.0
'@sentry/node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

Ensure to test the '@sentry/node' package thoroughly after updating to the new version 7.111.0 in the 'pnpm-lock.yaml' file.

'@sentry/profiling-node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

The '@sentry/profiling-node' package version in the 'pnpm-lock.yaml' file has been updated to 7.111.0. Make sure this does not cause any unexpected issues with profiling.

@@ -107,7 +107,7 @@ importers:
dependencies:
'@sentry/node':
specifier: ^7.102.0
version: 7.110.1
Copy link

Choose a reason for hiding this comment

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

The '@sentry/node' package version has been updated in multiple places within the 'pnpm-lock.yaml' file. Please confirm that all dependencies of this package are correctly updated.

@@ -1248,17 +1248,17 @@ packages:
Copy link

Choose a reason for hiding this comment

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

@sentry/node has been updated correctly in resolution, but make sure to test because this is a major dependency in this system.

'@sentry/types': 7.110.1
'@sentry/utils': 7.110.1
'@sentry-internal/tracing': 7.111.0
'@sentry/core': 7.111.0
Copy link

Choose a reason for hiding this comment

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

Version update spotted in '@sentry/profiling-node'. Test to make sure the new version doesn't break any functionalities.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

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

The changes in this commit primarily update version numbers for various packages in the package.json and pnpm-lock.yaml files. It's important to ensure these updates don't introduce breaking changes or conflicts with other packages. If the testing passes for this commit and there are no noticeable issues in runtime, then these changes are generally fine. Overall, the changes appear routine and are unlikely to introduce major issues.

@@ -26,8 +26,8 @@
},
"devDependencies": {
"@eslint/js": "^9.0.0",
"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

This line updates @sentry/node library to a new version. While this might be necessary, it's always a good idea to verify what changes were introduced in this new version in relation to the project using it.

"@sentry/node": "7.110.1",
"@sentry/profiling-node": "7.110.1",
"@sentry/node": "7.111.0",
"@sentry/profiling-node": "7.111.0",
Copy link

Choose a reason for hiding this comment

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

Once again a version upgrade for a library from @sentry. Same steps apply as in the previous comment: check for potential breaking changes introduced in version 7.111.0.

@@ -49,11 +49,11 @@ importers:
specifier: ^9.0.0
version: 9.0.0
'@sentry/node':
specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
Copy link

Choose a reason for hiding this comment

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

@sentry node version is updated in the pnpm-lock.yaml as well, which is good for consistency, make sure the changes in the new version do not break existing functionality.

specifier: 7.110.1
version: 7.110.1
specifier: 7.111.0
version: 7.111.0
Copy link

Choose a reason for hiding this comment

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

The specified version of @sentry/profiling-node is updated here. Check the CHANGELOG or release notes for this version update.

/@sentry-internal/tracing@7.110.1:
resolution: {integrity: sha512-4kTd6EM0OP1SVWl2yLn3KIwlCpld1lyhNDeR8G1aKLm1PN+kVsR6YB/jy9KPPp4Q3lN3W9EkTSES3qhP4jVffQ==}
/@sentry-internal/tracing@7.111.0:
resolution: {integrity: sha512-CgXly8rsdu4loWVKi2RqpInH3C2cVBuaYsx4ZP5IJpzSinsUAMyyr3Pc0PZzCyoVpBBXGBGj/4HhFsY3q6Z0Vg==}
engines: {node: '>=8'}
dependencies:
Copy link

Choose a reason for hiding this comment

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

@sentry/core version is updated. This is a core library and changes in this could potentially have significant impacts on your application, a thorough testing would be necessary ensure everything works as expected.

engines: {node: '>=8'}
dependencies:
'@sentry/core': 7.110.1
Copy link

Choose a reason for hiding this comment

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

@sentry/types version is updated. Verify the changes in version 7.111.0 to be sure they don't break any existing code.

@@ -1248,17 +1248,17 @@ packages:
- supports-color
Copy link

Choose a reason for hiding this comment

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

@sentry/node dependency's integrity checksum has changed due to a new version. It is standard behavior when package content changes.

engines: {node: '>=8'}
dependencies:
'@sentry-internal/tracing': 7.110.1
'@sentry/core': 7.110.1
Copy link

Choose a reason for hiding this comment

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

@sentry/profiling-node dependency's integrity checksum has changed due to a new version, which is expected.

@@ -1267,15 +1267,15 @@ packages:
Copy link

Choose a reason for hiding this comment

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

@sentry/types checksum has changed, ensure that it is reflected wherever the dependency has been used.

@@ -1267,15 +1267,15 @@ packages:
node-abi: 3.56.0
dev: true

/@sentry/types@7.110.1:
resolution: {integrity: sha512-sZxOpM5gfyxvJeWVvNpHnxERTnlqcozjqNcIv29SZ6wonlkekmxDyJ3uCuPv85VO54WLyA4uzskPKnNFHacI8A==}
/@sentry/types@7.111.0:
Copy link

Choose a reason for hiding this comment

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

@sentry/utils checksum changed as the version has been updated. As with all package updates, please ensure this update works with the rest of the project code.

Copy link

codecov bot commented Apr 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.50%. Comparing base (006f1af) to head (1536b90).

✅ All tests successful. No failed tests found ☺️

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1898   +/-   ##
=======================================
  Coverage   42.50%   42.50%           
=======================================
  Files          83       83           
  Lines       10329    10329           
  Branches      126      126           
=======================================
  Hits         4390     4390           
  Misses       5939     5939           
Flag Coverage Δ *Carryforward flag
core 100.00% <ø> (ø) Carriedforward from 006f1af
database 14.21% <ø> (ø) Carriedforward from 006f1af
gateway 46.84% <ø> (ø) Carriedforward from 006f1af
lobby 32.69% <ø> (ø) Carriedforward from 006f1af
login 24.06% <ø> (ø) Carriedforward from 006f1af
patch 87.28% <ø> (ø) Carriedforward from 006f1af
persona 27.94% <ø> (ø) Carriedforward from 006f1af
shard 96.87% <ø> (ø) Carriedforward from 006f1af
transactions 52.52% <ø> (ø) Carriedforward from 006f1af

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot merged commit f8517d6 into main Apr 18, 2024
14 checks passed
@renovate renovate bot deleted the renovate/sentry-javascript-monorepo branch April 18, 2024 18:43
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.

0 participants