Skip to content

Conversation

@antonpirker
Copy link
Contributor

Deactivated deployment of Lambda Layer until new Lambda Extension is production ready.
With this we make sure, that we do not break existing Lambda Layer users.

@github-actions
Copy link
Contributor

size-limit report 📦

Path Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified) 19.33 KB (-4.04% 🔽)
@sentry/browser - ES5 CDN Bundle (minified) 59.9 KB (-7.29% 🔽)
@sentry/browser - ES6 CDN Bundle (gzipped + minified) 18.18 KB (-3.61% 🔽)
@sentry/browser - ES6 CDN Bundle (minified) 53.59 KB (-7.56% 🔽)
@sentry/browser - Webpack (gzipped + minified) 19.88 KB (-14.47% 🔽)
@sentry/browser - Webpack (minified) 63.04 KB (-22.86% 🔽)
@sentry/react - Webpack (gzipped + minified) 19.9 KB (-14.51% 🔽)
@sentry/nextjs Client - Webpack (gzipped + minified) 43.38 KB (-9.74% 🔽)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified) 24.98 KB (-4.2% 🔽)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified) 23.54 KB (-3.86% 🔽)

@lobsterkatie lobsterkatie changed the title ref(serverless): Deactivated deployment of Lambda Layer ref(serverless): Deactivate deployment of Lambda Layer May 23, 2022
@Lms24 Lms24 merged commit 5a782c3 into 7.x May 23, 2022
@Lms24 Lms24 deleted the antonpirker/deactivate-deploy-of-lambda-layer branch May 23, 2022 14:12
@antonpirker antonpirker restored the antonpirker/deactivate-deploy-of-lambda-layer branch May 23, 2022 14:30
@antonpirker antonpirker deleted the antonpirker/deactivate-deploy-of-lambda-layer branch May 23, 2022 14:31
AbhiPrasad pushed a commit that referenced this pull request May 30, 2022
…production ready (#5148)

Deactivated deployment of Lambda Layer until new Lambda Extension is production ready.
With this we make sure, that we do not break existing Lambda Layer users.
@AbhiPrasad AbhiPrasad added this to the 7.0.0 milestone May 30, 2022
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.

4 participants