-
Notifications
You must be signed in to change notification settings - Fork 26
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
publish: getsentry/[email protected] #4819
Comments
andreiborza
added a commit
to getsentry/sentry-release-registry
that referenced
this issue
Dec 27, 2024
…layer entries Manually removes the faulty releases that overwrote the node lambda layer with the suffixed version (`SentryNodeServerlessSDKv8`) and links to the last version (`8.45.1`) that had a correct entry for the layer (`SentryNodeServerlessSDK`). Docs and the product AWS Lambda integration are not correctly set up when the suffixed layer is the latest layer. Release [8.48.0](getsentry/publish#4819) will fix this again.
andreiborza
added a commit
to getsentry/sentry-release-registry
that referenced
this issue
Dec 27, 2024
…layer entries (#175) Manually removes the faulty releases that overwrote the node lambda layer with the suffixed version (`SentryNodeServerlessSDKv8`) and links to the last version (`8.45.1`) that had a correct entry for the layer (`SentryNodeServerlessSDK`). Docs and the product AWS Lambda integration are not correctly set up when the suffixed layer is the latest layer. Release [8.48.0](getsentry/publish#4819) will fix this again.
#retract |
Release request retracted by @andreiborza. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requested by: @andreiborza
Merge target: v8
Quick links:
Assign the accepted label to this issue to approve the release.
Leave a comment containing
#retract
under this issue to retract the release (original issuer only).Targets
Targets marked with a checkbox have already been executed. Administrators can manually tick a checkbox to force craft to skip it.
The text was updated successfully, but these errors were encountered: