fix(sidecar): invalid semver range for source-map#667
Merged
BYK merged 3 commits intogetsentry:mainfrom Jan 23, 2025
Merged
Conversation
|
@belgattitude is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
Member
|
Heya, thanks for the report and the fix! I'll see why there are so many changes in the lock file and approve, merge, release. |
BYK
approved these changes
Jan 23, 2025
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #667 +/- ##
=======================================
Coverage 31.29% 31.29%
=======================================
Files 92 92
Lines 5435 5435
Branches 100 100
=======================================
Hits 1701 1701
Misses 3734 3734 ☔ View full report in Codecov by Sentry. |
BYK
pushed a commit
that referenced
this pull request
Jan 24, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @spotlightjs/astro@2.4.1 ### Patch Changes - Updated dependencies \[]: - @spotlightjs/spotlight@2.10.1 ## @spotlightjs/electron@1.4.1 ### Patch Changes - Updated dependencies \[[`03e386af2024eda44c02952a06433e4d4ecb3356`](03e386a), [`416fecd778d4829d490b07ec4d500946fa439210`](416fecd)]: - @spotlightjs/overlay@2.10.1 - @spotlightjs/sidecar@1.11.1 ## @spotlightjs/overlay@2.10.1 ### Patch Changes - fix: Always try to use sidecar along with direct SDK transport ([#672](#672)) ## @spotlightjs/sidecar@1.11.1 ### Patch Changes - Fix invalid semver range for source-map dependency ([#667](#667)) ## @spotlightjs/spotlight@2.10.1 ### Patch Changes - Updated dependencies \[[`03e386af2024eda44c02952a06433e4d4ecb3356`](03e386a), [`416fecd778d4829d490b07ec4d500946fa439210`](416fecd)]: - @spotlightjs/overlay@2.10.1 - @spotlightjs/sidecar@1.11.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
dcramer
pushed a commit
that referenced
this pull request
Jun 3, 2025
Fixes #668 ## Issue The range specified isn't technically correct (pnpm accepts this though). Check with semver  The fix is simple:  ## Workaround till fixed upstream ```json5 "resolutions": { "source-map": ">=0.8.0-beta <0.9.0" }, ```
dcramer
pushed a commit
that referenced
this pull request
Jun 3, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action to publish automatically](https://github.com/changesets/action#with-publishing). If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @spotlightjs/astro@2.4.1 ### Patch Changes - Updated dependencies \[]: - @spotlightjs/spotlight@2.10.1 ## @spotlightjs/electron@1.4.1 ### Patch Changes - Updated dependencies \[[`03e386af2024eda44c02952a06433e4d4ecb3356`](03e386a), [`416fecd778d4829d490b07ec4d500946fa439210`](416fecd)]: - @spotlightjs/overlay@2.10.1 - @spotlightjs/sidecar@1.11.1 ## @spotlightjs/overlay@2.10.1 ### Patch Changes - fix: Always try to use sidecar along with direct SDK transport ([#672](#672)) ## @spotlightjs/sidecar@1.11.1 ### Patch Changes - Fix invalid semver range for source-map dependency ([#667](#667)) ## @spotlightjs/spotlight@2.10.1 ### Patch Changes - Updated dependencies \[[`03e386af2024eda44c02952a06433e4d4ecb3356`](03e386a), [`416fecd778d4829d490b07ec4d500946fa439210`](416fecd)]: - @spotlightjs/overlay@2.10.1 - @spotlightjs/sidecar@1.11.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before opening this PR:
pnpm changeset:addIssue
The range specified isn't technically correct (pnpm accepts this though). Check with semver
The fix is simple:
Workaround till fixed upstream