Today we are announcing our $1M seed round. The new funding helps us in our mission to build the future of serverless. Read more about our announcement here:
https://t.co/PoJ4LoE0Kx
We've introduced a new type of build image — General Purpose Latest
It stays updated to the latest runtimes, security patches, and will be cached by default; making it faster and more secure.
It'll be the default moving forward.
More on it here: https://t.co/PRF4d4tMlq
Seed now supports deploying through IAM roles. It's far more secure than IAM users.
While your IAM user credentials will continue to work, we recommend that you upgrade your credentials.
Read more:
https://t.co/XddRxIC1VA
We rolled out a major update to the @SST_dev Guide — https://t.co/mvh9Yq4Bxk
Here are a few things we've updated:
- TypeScript by default
- We also use @pnpmjs
- For our React app on the frontend we are using @vite_js (Create React App has been deprecated)
- For handling secrets, we are using the `sst secrets` CLI
- We also archived all of our older chapters
A huge shoutout to Christine Panus — https://t.co/173QeWW2dp for an incredibly detailed PR with these changes. This update would not have been possible without her contributions.
Oh and as a bonus https://t.co/tnJXKv4dP0 is now deployed with SST and @SEED_run — https://t.co/agwxsIDHwp
We are hosting a special virtual event to show off the next generation of serverless tools and creators.
And we couldn't be more excited about the lineup of speakers.
https://t.co/Mn4LlJMGVC
We added a highly requested feature.
You can now filter the PRs that are auto-deployed in Seed.
So `feature/**` would only auto-deploy PRs that have source branches that match this pattern.
Read more here:
https://t.co/GWM5RVQi9F
Another update:
We don't have an official word from AWS but all the builds are back to normal. Our fallback infrastructure is performing normally as well.
All the previously queued builds have also completed executing.
An update on this issue:
1. We increased the capacity of our primary infrastructure to reduce the chances of a fallback.
2. We heard back from AWS that the root cause will be fixed in an hour or two.
An update on this issue:
1. We increased the capacity of our primary infrastructure to reduce the chances of a fallback.
2. We heard back from AWS that the root cause will be fixed in an hour or two.
We are having some issues with our fallback build infrastructure.
This is causing some builds to be queued for way too long.
We are investigating the issue and working on a temporary fix.