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 against serverless v3 #1812

Merged
merged 1 commit into from
May 21, 2024
Merged

Fix against serverless v3 #1812

merged 1 commit into from
May 21, 2024

Conversation

mnapoli
Copy link
Member

@mnapoli mnapoli commented May 21, 2024

Serverless Framework has started releasing a beta version as a stable version on NPM.

This breaks all the existing systems and tutorials out there because it requires a license key now. To fix the CI, and to make life easier for newcomers, I'm updating the instructions to install v3.

@mnapoli mnapoli merged commit 88af90f into master May 21, 2024
8 checks passed
@mnapoli mnapoli deleted the fix-serverless branch May 21, 2024 19:16
@stloyd stloyd mentioned this pull request May 23, 2024
@cybage-kmistry
Copy link

Yes using serverless with v3 explicitly will resolve this issue. But going forward we are not going to upgrade to v4 of serverless with bref?

@nadar
Copy link

nadar commented May 24, 2024

would be interesting to know @mnapoli where things are going with bref, having serverless v4 in mind (which is an absolute pain 😢 )

@cybage-kmistry
Copy link

@mnapoli @nadar May be something with AWS SAM which is as simple as doing deployment with bref.

@KorvinSzanto
Copy link

@mnapoli @nadar May be something with AWS SAM which is as simple as doing deployment with bref.

Bref already has CDK templates that work great: https://github.com/brefphp/constructs

@mnapoli
Copy link
Member Author

mnapoli commented May 24, 2024

Hey all, my current stance: #1815 (comment)

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