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(v7/publish): Ensure discontinued packages are published with latest tag #14926

Merged
merged 2 commits into from
Jan 9, 2025

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Jan 7, 2025

This PR sets the NPM publish tag of discontinued packages from v7 back to latest. As pointed out in #14923, it's a bit misleading for packages that have not received a v8 version but newer v7 versions that their latest tag doesn't point to the in fact latest version.

Affected packages:

  • @sentry/angular-ivy (replaced by @sentry/angular in v8)
  • @sentry/hub (discontinued)
  • @sentry/tracing (discontinued)
  • @sentry/serverless (replaced by @sentry/aws-serverless, @sentry/google-cloud and @sentry/node respectively)

fixes #14923

@Lms24 Lms24 requested review from a team as code owners January 7, 2025 15:15
@Lms24 Lms24 changed the base branch from develop to v7 January 7, 2025 15:16
@Lms24 Lms24 removed request for a team January 7, 2025 15:16
@Lms24 Lms24 self-assigned this Jan 7, 2025
@Lms24 Lms24 requested review from lforst and mydea January 7, 2025 15:20
@mydea
Copy link
Member

mydea commented Jan 8, 2025

We need to remember to do the same for core & types in v8, when this ships!

@Lms24 Lms24 merged commit e779b43 into v7 Jan 9, 2025
104 checks passed
@Lms24 Lms24 deleted the lms/fix-publish-latest-tag-discontinued-packages branch January 9, 2025 14:48
Lms24 added a commit that referenced this pull request Jan 9, 2025
Cutting a v7 patch to fix the label assignment of discontinued packages
(see #14926)
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.

2 participants