You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mismatch between latest npm tag and actual latest available version for @sentry/serverless #14923
Even though the package is no longer published in v7 as it moved to @sentry/aws-serverless in v8, it's unexpected IMO that the latest npm tag is not getting updated, since there are backport fixes available after 7.114.0.
Expected Result
latest npm tag is pointing to 7.114.0, even though 7.120.2 is the actual latest version published (tag v7).
changed the title [-]Mismatch being `latest` npm tag and latest available version for `@sentry/serverless`[/-][+]Mismatch between `latest` npm tag and actual latest available version for `@sentry/serverless`[/+]on Jan 7, 2025
Hi @rdsedmundo thanks for writing in! We discussed this briefly internally and we'll change the publishing tag back to latest for packages that were discontinued with the release of version 8 of the SDK. Good catch, thanks!
Hi @rdsedmundo we just released 7.120.3 and @sentry/serverlessas well as other discontinued packages in v7 now have the latest tag set on the new version. Closing this issue. Thanks again for reporting!
Activity
[-]Mismatch being `latest` npm tag and latest available version for `@sentry/serverless`[/-][+]Mismatch between `latest` npm tag and actual latest available version for `@sentry/serverless`[/+]Lms24 commentedon Jan 7, 2025
Hi @rdsedmundo thanks for writing in! We discussed this briefly internally and we'll change the publishing tag back to
latestfor packages that were discontinued with the release of version 8 of the SDK. Good catch, thanks!fix(v7/publish): Ensure discontinued packages are published with `lat…
Lms24 commentedon Jan 10, 2025
Hi @rdsedmundo we just released 7.120.3 and
@sentry/serverlessas well as other discontinued packages in v7 now have thelatesttag set on the new version. Closing this issue. Thanks again for reporting!