8000 9.18.0 introduces a dependency on a public repository which fails on machines without Git installed · Issue #16281 · getsentry/sentry-javascript · GitHub
[go: up one dir, main page]
Skip to content

9.18.0 introduces a dependency on a public repository which fails on machines without Git installed #16281

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.

Sign up for GitHub

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

Jump to bottom
Closed
3 tasks done
raglan-road opened this issue May 13, 2025 · 4 comments · Fixed by #16287
Closed
3 tasks done

9.18.0 introduces a dependency on a public repository which fails on machines without Git installed #16281

raglan-road opened this issue May 13, 2025 · 4 comments · Fixed by #16287
Assignees
@andreiborza
Labels
Bug Next.js

Comments

@raglan-road
Copy link

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

9.18.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

  • Install or update Sentry to 9.18.0 on a VM without Git installed. For example, the nodejs Alpine linux distro.
  • Run an npm install or a build.
  • When the Sentry package attempts to install the @fastify/otel dependency, it does so using Git, which isn't there, so the install fails.

Expected Result

Sentry is able to load its dependencies and the build succeeds or the requirement for Git to be installed on the target machine is documented as a potentially breaking change.

Actual Result

The build fails when the Sentry package attempts to install its dependency on the forked version of @fastify/otel as it installs via Git, which does not necessarily exist on the target machine.

Rolling back to 9.16.1 fixes the issue as the new dependency isn't there.
@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 May 13, 2025
@andreiborza
Copy link
Member

Hi @raglan-road, thanks for filing this.

Can confirm, it indeed fails to install because of our @fastify/otel fork. Will look into it.

@andreiborza andreiborza self-assigned this May 13, 2025
@jpmcb
Copy link
jpmcb commented May 13, 2025

+1 - I would consider this a major regression - this breaks packages that depend on @sentry/node and don't pin to an older version which, before 9.18, worked with no dependency on git (like Windows machines, Macs that don't have Xcode dev tools setup, VSCode dev containers, etc. etc.):

Replication steps:

  1. Start fedora 43 container
docker run -it --rm fedora:43 /bin/bash
  1. Install node
dnf install nodejs22
  1. Attempt to install sentry node package:
bash-5.2# npm i -g @sentry/node
npm error code ENOENT
npm error syscall spawn git
npm error path git
npm error errno -2
npm error enoent An unknown git error occurred
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-05-13T22_14_22_036Z-debug-0.log

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 May 13, 2025
@andreiborza andreiborza mentioned this issue May 14, 2025
Merged
@andreiborza
Copy link
Member

Thanks, we'll release a fix soon.

@github-actions GitHub Actions
Copy link
Contributor

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16287, which was included in the 9.19.0 release.

@andreiborza andreiborza mentioned this issue May 15, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andreiborza andreiborza

Labels
Bug Next.js
Projects
GitHub Issues with 👀 3
Archived in project
Milestone
No milestone
3 participants
@raglan-road @jpmcb @andreiborza
0