Skip to content

[v9] Drop Deno v1 support and discontinue publishing on Deno land #15009

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

Closed
timfish opened this issue Jan 14, 2025 · 0 comments
Closed

[v9] Drop Deno v1 support and discontinue publishing on Deno land #15009

timfish opened this issue Jan 14, 2025 · 0 comments
Assignees
Labels
Meta: Breaking Package: deno Issues related to the Sentry Deno SDK
Milestone

Comments

@timfish
Copy link
Collaborator

timfish commented Jan 14, 2025

Description

The deno.land registry has been deprecated in favour of JSR.

However, Deno v2 now has full Node and npm support.

Removing support for Deno v1 would simplify a lot.

If we drop support for v1 we could suggest customers just use @sentry/node with Deno but they would have to allow all permissions and we already have Deno specific transport and integrations that respect Deno's permissions model.

@timfish timfish added Meta: Breaking Package: deno Issues related to the Sentry Deno SDK labels Jan 14, 2025
@timfish timfish added this to the 9.0.0 milestone Jan 14, 2025
@timfish timfish self-assigned this Jan 14, 2025
@lforst lforst changed the title @sentry/deno for v9 [v9] Drop Deno v1 support and discontinue publishing on Deno land Jan 20, 2025
@lforst lforst self-assigned this Jan 22, 2025
@lforst lforst closed this as completed Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta: Breaking Package: deno Issues related to the Sentry Deno SDK
Projects
None yet
Development

No branches or pull requests

2 participants