This repository has been archived by the owner on Sep 8, 2023. It is now read-only.
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.
📝 Description
Features
>=14.0.0
;AssertError
, which we don't use.For v11 the least allowed was set to
v11.0.1
, because v11.0.0 was marked as deprecated. It was missing an important part of release, fixed in v11.0.1.Both versions are compatible with our package:
>=14.0.0
;eslint-config-hapi
andeslint-plugin-hapi
) with the single @hapi/eslint-plugin at the latest version (v6.0.0).Other Changes
@semantic-release/changelog
(v6.0.1 -> v6.0.2)commitizen
(v4.2.5 -> v4.3.0)eslint
(v5.16.0 -> v8.33.0)joi
(v17.6.0 -> v17.7.0)nyc
(v14.1.1 -> v15.1.0)semantic-release
(v19.0.3 -> v19.0.5)tape
(v4.16.0 -> v5.6.3)dot-prop
at v7.0.0 became ESM-onlysemantic-release
at v20.0.0 became ESM-only with Node.js v18+ requirement