We're happy to announce v1.7 of the Serverless Framework! Let's take a look at the release highlights.
Note: You can find a complete list of all the updates in the changelog.
Have you ever wanted to connect custom CloudWatch rules to fire your Lambda functions?
Serverless v1.7 has you covered and introduces the new
cloudwatchEvent event source!
Here's an example of how the new
cloudwatchEvent can be used:
functions: notifier: handler: handler.notifier events: - cloudwatchEvent: event: source: - "aws.ec2" detail-type: - "EC2 Instance State-change Notification" detail: state: - pending
You can learn more about the new CloudWatch Event support in the corresponding documentation.
We heard you and we agree that introducing breaking changes can be pretty painful.
With this release we introduce logging messages that will show you what breaking changes will be introduced in the next release (v1.8 in this case).
You'll see them by default after upgrading to the new Serverless version but you can also disable them if you don't want to see them anymore.
The idea here is to inform you about all the upcoming breaking changes coming in the next release.
This should give you enough time to update your codebase so that Serverless will run smoothly.
As usual we keep the breaking changes as minimal as possible so that updating from one version to the next shouldn't be too hard.
Serverless is increasingly being used in CI/CD systems. The resources (i.e. CPU or Memory) of those systems often tend to be limited.
This release introduces a one-line bug fix that reduces the memory consumption during the zipping process by about ~40%.
This should make it easier for you to use Serverless on a less powerful machine like a CI/CD system.
We've also fixed some nasty bugs and introduced some enhancements.
Thanks for reporting bugs and opening issues to improve Serverless!
Here's a list of all the breaking changes that will be introduced in Serverless v1.8.
Note: You'll see the same list in the CLI if you run a Serverless command (as long as you haven't disabled it).
You'll always get the most recent list of breaking changes when you take a look at the upcoming milestone or in the Serverless CLI.
This release contains lots of hard work from our awesome community and wouldn't have been possible without passionate people contributing to Serverless.
Here's a list of all the contributors who've PR'd changes for this release:
Serverless has a really helpful, awesome and vibrant community. Do you want to help us develop the best Serverless toolings out there?
Contributing isn't just about code! Chime in on discussion, help with documentation updates or review PRs.
We recently introduced our newest open source effort - "Scope". It's a tool that gives you a bird's eye view of your GitHub project.
We built this tool to scratch our own itch of maintaining and guiding the development process of the Serverless Framework.
A deployed version for our Serverless Framework repository can be found here:
Here you can see all the current discussions, to-be-reviewed PRs and recently closed issues and PRs.
You can use this status board to see all the important stuff that's currently happening in the Framework development phase.
The Serverless Examples Repository is an excellent resource if you want to explore some real world examples and learn more about what Serverless architectures look like.
To get started, pop open your terminal & run
npm install serverless -g
Join 12,000+ other serverless devs & keep up to speed on the latest serverless trends