Skip to content

Conversation

@AbhiPrasad
Copy link
Member

closes #5665

Goodbye hub package, I've known you my whole (sentry) life.

Moved tests into core where applicable, otherwise deleted tests that were redundant.

@AbhiPrasad AbhiPrasad requested a review from a team February 6, 2024 18:21
@AbhiPrasad AbhiPrasad self-assigned this Feb 6, 2024
@AbhiPrasad AbhiPrasad requested review from Lms24 and mydea and removed request for a team February 6, 2024 18:21
@mydea
Copy link
Member

mydea commented Feb 7, 2024

I wonder if we should hold off with that, just to avoid f**ing with craft releases? 🤔
An alternative approach I thought of was to delete all code from the package, but leave the package intact for now (simply exporting nothing)..? WDYT?

@AbhiPrasad AbhiPrasad merged commit 465bd29 into develop Feb 8, 2024
@AbhiPrasad AbhiPrasad deleted the abhi-delete-hub branch February 8, 2024 14:02
Lms24 added a commit that referenced this pull request Feb 14, 2024
Lms24 added a commit that referenced this pull request Feb 14, 2024
Since we deleted `@sentry/hub` in #10530, we also removed the craft NPM
target for the hub package. Given that the craft config is always taken
from `develop` (generally, the default branch of the repository), Craft
no longer published `@sentry/hub` when we cut a release from our `v7`
branch.

Unfortunately, the NPM target does not support an optional
`onlyIfPresent` configuration, meaning for now, we have to continue
publishing a `@sentry/hub` placeholder package when we cut a release
from `develop` (i.e. our v8 branch at the moment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v8] Remove @sentry/hub package

3 participants