graphql-binding chore(deps): update dependency semantic-release to v19

chore(deps): update dependency semantic-release to v19

Open renovate[bot] opened this issue 4 years ago • 0 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	`15.13.24` -> `19.0.3`

Release Notes

semantic-release/semantic-release

`v19.0.3`

Compare Source

Bug Fixes

log-repo: use the original form of the repo url to remove the need to mask credentials (#2459) (58a226f), closes #2449

`v19.0.2`

Compare Source

Bug Fixes

npm-plugin: upgraded to the stable version (0eca144)

`v19.0.1`

Compare Source

Bug Fixes

npm-plugin: upgraded to the latest beta version (8097afb)

`v19.0.0`

Compare Source

Bug Fixes

npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
upgrade marked to resolve ReDos vulnerability (#2330) (d9e5bc0)

BREAKING CHANGES

npm-plugin: @semantic-release/npm has also dropped support for node v15
node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

`v18.0.1`

Compare Source

Bug Fixes

bump @semantic-release/commit-analyzer to 9.0.2 (#2258) (7f971f3)

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

`v17.4.7`

Compare Source

Bug Fixes

engines: fixed defined node version to account for the higher requirement from the npm plugin (#2088) (ea52e17)

`v17.4.6`

Compare Source

Bug Fixes

marked: reverted upgrade to v3 (#2087) (5edff69)

`v17.4.5`

Compare Source

Bug Fixes

deps: update dependency marked to v3 (6e4beb8)

`v17.4.4`

Compare Source

Bug Fixes

corrected spelling of invalid plugin config error (#1979) (80e1665)

`v17.4.3`

Compare Source

Bug Fixes

bump minimal version of lodash to address CVE-2021-23337 (#1931) (55194c1)

`v17.4.2`

Compare Source

Bug Fixes

deps: update dependency hosted-git-info to v4 (#1838) (44b3344)

`v17.4.1`

Compare Source

Bug Fixes

deps: peer dependecy error with marked-terminal (#1829) (07f12b9)

`v17.4.0`

Compare Source

Features

config: Use cosmiconfig defaults to support .cjs config files (#1815) (3ecc196), closes #1814

`v17.3.9`

Compare Source

Bug Fixes

update link to GitLab CI introduction (#1794) (a9be97b)

`v17.3.8`

Compare Source

Bug Fixes

deps: update dependency marked to v2 (a2eaed0)

`v17.3.7`

Compare Source

Bug Fixes

deps: update dependency get-stream to v6 (#1748) (969e460)

`v17.3.6`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v7 (#1742) (cc74a4c)
deps: update dependency execa to v5 (#1745) (8262832)

`v17.3.5`

Compare Source

Bug Fixes

pin initial branch to master (#1740) (32a2c91)

`v17.3.4`

Compare Source

Bug Fixes

deps: update to yargs 16.2.0 (#1739) (d2ec893)

`v17.3.3`

Compare Source

Bug Fixes

add logging for top-level errors (#1736) (9f57b84)

`v17.3.2`

Compare Source

Bug Fixes

normalize ci: false into noCi: true after configs get merged (#1732) thanks @dominykas (21c151f)

`v17.3.1`

Compare Source

Bug Fixes

deps: Require find-versions ^4.0.0 (#1722) (52238cb)

`v17.3.0`

Compare Source

Features

docs: note that publish token is required (#1700) (885d87a)

`v17.2.4`

Compare Source

Bug Fixes

escape uri encoded symbols (#1697) (f8f8fbc)

`v17.2.3`

Compare Source

Bug Fixes

mask secrets when characters get uri encoded (ca90b34)

`v17.2.2`

Compare Source

Bug Fixes

don't parse port as part of the path in repository URLs (#1671) (77a75f0)
use valid git credentials when multiple are provided (#1669) (2bf3771)

`v17.2.1`

Compare Source

Reverts

Revert "feat: throw an Error if package.json has duplicate "repository" key (#1656)" (3abcbaf), closes #1656 #1657

`v17.2.0`

Compare Source

Features

throw an Error if package.json has duplicate "repository" key (#1656) (b8fb35c)

`v17.1.2`

Compare Source

Bug Fixes

add logging for when ssh falls back to http (#1639) (b4c5d0a)

`v17.1.1`

Compare Source

Bug Fixes

use correct ci branch context (#1521) (0f0c650)

`v17.1.0`

Compare Source

Features

bitbucket-basic-auth: support for bitbucket server basic auth (#1578) (a465801)

`v17.0.8`

Compare Source

Bug Fixes

prevent false positive secret replacement for Golang projects (#1562) (eed1d3c)

`v17.0.7`

Compare Source

Bug Fixes

package: update marked to version 1.0.0 (#1534) (d64db31)

`v17.0.6`

Compare Source

Bug Fixes

adapt for semver to version 7.3.2 (part II) (#1530) (431d571)

`v17.0.5`

Compare Source

Bug Fixes

adapt for semver to version 7.3.2 (0363790)

`v17.0.4`

Compare Source

Bug Fixes

add repositoryUrl in logs (55be0ba)

`v17.0.3`

Compare Source

Bug Fixes

pass a branch name to getGitAuthUrl (e7bede1)

`v17.0.2`

Compare Source

Bug Fixes

package: update marked-terminal to version 4.0.0 (8ce2d6e)

`v17.0.1`

Compare Source

Bug Fixes

package: update @semantic-release/commit-analyzer to version 8.0.0 (45695b9)
package: update @semantic-release/github to version 7.0.0 (c48bd3a)
package: update @semantic-release/npm to version 7.0.0 (f2b5826)
package: update @semantic-release/release-notes-generator to version 9.0.0 (3c7b114)

`v17.0.0`

Compare Source

BREAKING CHANGES

Require Node.js >= 10.18

`v16.0.4`

Compare Source

Bug Fixes

correct error when remote repository has no branches (c6b1076)

`v16.0.3`

Compare Source

Bug Fixes

use --no-verify when testing the Git permissions (b54b20d)

`v16.0.2`

Compare Source

Bug Fixes

fetch tags on repo cached by the CI (6b5b02e)

`v16.0.1`

Compare Source

Bug Fixes

package: update env-ci to version 5.0.0 (3739ab5)

`v16.0.0`

Compare Source

BREAKING CHANGES

⚠️ For v16.0.0@beta users only:

In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the @{channel} suffix is no longer necessary.

The tags formatted as v{version}@{channel} will now be ignored. If you have releases using this format you will have to upgrade them:
- Find all the versions that have been released on a branch other than the default one by searching for all tags formatted as v{version}@{channel}
- For each of those version:
  - Create a tag without the {@channel} if none doesn't already exists
  - Add a Git note to the tag without the {@channel} containing the channels on which the version was released formatted as {"channels":["channel1","channel2"]} and using null for the default channel (for example.{"channels":[null,"channel1","channel2"]})
  - Push the tags and notes
  - Update the GitHub releases that refer to a tag formatted as v{version}@{channel} to use the tag without it
  - Delete the tags formatted as v{version}@{channel}
Require Node.js >= 10.13
Git CLI version 2.7.1 or higher is now required: The --merge option of the git tag command has been added in Git version 2.7.1 and is now used by semantic-release
Regexp are not supported anymore for property matching in the releaseRules option.

Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.
The branch option has been removed in favor of branches
The new branches option expect either an Array or a single branch definition. To migrate your configuration:
- If you want to publish package from multiple branches, please see the configuration documentation
- If you use the default configuration and want to publish only from master: nothing to change
- If you use the branch configuration and want to publish only from one branch: replace branch with branches ("branch": "my-release-branch" => "branches": "my-release-branch")

Features

allow addChannel plugins to return false in order to signify no release was done (e1c7269)
allow publish plugins to return false in order to signify no release was done (47484f5)
allow to release any version on a branch if up to date with next branch (916c268)
support multiple branches and distribution channels (7b40524)
use Git notes to store the channels on which a version has been released (b2c1b2c)
package: update @semantic-release/commit-analyzer to version 7.0.0 (e63e753)

Performance Improvements

use git tag --merge <branch> to filter tags present in a branch history (cffe9a8)

Bug Fixes

add channel to publish success log (5744c5e)
add a flag indicate which branch is the main one (2caafba)
Add helpful detail to ERELEASEBRANCHES error message (#1188) (37bcc9e)
allow multiple branches with same channel (63f51ae)
allow to set ci option via API and config file (2faff26)
call getTagHead only when necessary (de77a79)
call success plugin only once for releases added to a channel (9a023b4)
correct log when adding channel to tag (61665be)
correctly determine next pre-release version (0457a07)
correctly determine release to add to a channel (aec96c7)
correctly handle skipped releases (89663d3)
display erroring git commands properly (1edae67)
do not call addChannelfor 2 merged branches configured with the same channel (4aad9cd)
do not create tags in dry-run mode for released to add to a channel (97748c5)
fetch all release branches on CI (b729183)
fix branch type regexp to handle version with multiple digits (52ca0b3)
fix maintenance branch regex (a022996)
fix range regexp to handle version with multiple digits (9a04e64)
handle branch properties set to false (751a5f1)
harmonize parameters passed to getError (f96c660)
ignore lasst release only if pre-release on the same channel as current branch (990e85f)
increase next version on prerelease branch based on highest commit type (9ecc7a3)
look also for previous prerelease versions to determine the next one (9772563)
modify fetch function to handle CircleCI specifics (cbef9d1)
on maintenance branch add to channel only version >= to start range (c22ae17)
remove confusing logs when searching for releases to add to a channel (162b4b9)
remove hack to workaround GitHub Rebase & Merge (844e0b0)
remove unnecessary await (9a1af4d)
simplify get-tags algorithm (00420a8)
throws error if the commit associated with a tag cannot be found (1317348)
update plugin versions (0785a84)
update plugins dependencies (9890584)
verify is branch is up to date by comparing remote and local HEAD (a8747c4)
remove unnecessary branch parameter from push function (968b996)
revert to the correct refspec in fetch function (9948a74)
update plugins dependencies (73f0c77)
repositoryUrl: on beta repositoryUrl needs auth for pre-release flows (#1186) (3610422)