-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Provide an AWS lambda layer for v7 #12098
Labels
Comments
andreiborza
added a commit
that referenced
this issue
May 17, 2024
andreiborza
added a commit
that referenced
this issue
May 17, 2024
Closing this since v7 is lower prio and we can probably live with the current state of the docs. |
This was referenced Jun 3, 2024
This was referenced Jun 4, 2024
This was referenced Jun 4, 2024
This was referenced Jun 8, 2024
This was referenced Jun 9, 2024
This was referenced Jun 11, 2024
This was referenced Jun 12, 2024
This was referenced Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
Currently, we publish our AWS Lambda layer under the name
SentryNodeServerlessSDK
and each release we bump the version number by one (e.g. for SDK release8.2.1
the current version number for the layer is243
).This worked fine for us in the past, but now with v8 out, we do not want to overwrite the current v8 layer with a v7 layer when we do SDK releases for v7.
Solution Brainstorm
We should create a new lambda layer named
SentryNodeServerlessSDKV7
and exclusively publish to it when doing v7 releases.SentryNodeServerlessSDK
should always remain the layer name for the latest major version of the SDK, with previous majors getting their own layer names.Tasks
The text was updated successfully, but these errors were encountered: