Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
[email protected]
Major Changes
deps: Require Node.js 14.18+ (#760)
Node.js 12 will reach end of life by April 2022. The
semantic-release
package and stable--enable-source-maps
flag necessitate this new minimum version.Consider upgrading the Node.js version for your project across:
.nvmrc
package.json#/engines/node
.buildkite/pipeline.yml
,Dockerfile
, etc.)deps: semantic-release ^19.0.0 (#757)
Resolves SNYK-JS-MARKED-2342073 and SNYK-JS-MARKED-2342082.
This may alleviate the following
skuba release
error:template: Use
--enable-source-maps
(#761)Stable source map support has landed in Node.js 14.18+ via the built-in
--enable-source-maps
option.We recommend migrating off of custom source map implementations in favour of this option. Upgrading to skuba-dive v2 will remove
source-map-support
from theskuba-dive/register
hook.For a containerised application, update your Dockerfile:
For a Serverless Lambda application, update your
serverless.yml
:For a CDK Lambda application, update your stack:
Patch Changes
template/lambda-sqs-worker: Disable
tty
on deploy step (#753)Serverless Framework v3 renders progress spinners on interactive terminals. We recommend disabling tty in CI/CD for cleaner log output.
template/lambda-sqs-worker: serverless ^3.0.0 (#748)
template/lambda-sqs-worker: Replace
custom.env
configuration withparams
(#752)You can now define environment specific variables using the new Serverless parameters feature. See https://www.serverless.com/framework/docs/guides/parameters for more details.
template/*-rest-api: seek-jobs/gantry v1.6.1 (#759)
template/lambda-sqs-worker: Remove
provider.lambdaHashingVersion
(#751)This resolves the following deprecation warning in Serverless Framework v3:
Setting "20201221" for "provider.lambdaHashingVersion" is no longer effective as new hashing algorithm is now used by default. You can safely remove this property from your configuration.
deps: eslint-config-skuba 1.0.14 (#758)
This disables the
tsdoc/syntax
ESLint rule in tests for compatibility with/** @jest-environment env */
directives.deps: isomorphic-git ^1.11.1 (#750)
Resolves SNYK-JS-SIMPLEGET-2361683.