chore(deps): update dependency semantic-release to v23 #54

renovate · 2018-09-09T05:29:08Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	`12.4.1` -> `23.0.8`

Release Notes

semantic-release/semantic-release (semantic-release)

`v23.0.8`

Compare Source

Bug Fixes

deps: rename read-pkg-up -> read-package-up (4980cba)
deps: rename read-pkg-up -> read-package-up (#3249) (95a8b9e)

Bug Fixes

deps: update dependency marked to v12 (#3176) (38105f5)

`v23.0.1`

Compare Source

Bug Fixes

deps: update dependency marked-terminal to v7 (9faded8)

`v23.0.0`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v9 (#3105) (07dde04)
deps: update dependency marked to v11 (#3079) (6d2a6f1)
deps: upgraded to the latest version of env-ci (0d0ed9d)
use one note reference per tag to prevent conflicts (#2085) (020ea7d)

Features

node-versions: dropped support for node v18 and raised the minimum for v20 (2904832), closes /github.com/semantic-release/gitlab/pull/647#discussion_r1423131205

BREAKING CHANGES

deps: woodpecker ci users need to upgrade to v1.0.0 or higher to remain supported. see
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
node-versions: support for node v18 has been dropped and the minimum for v20 is now v20.8.1

related to https://github.com/semantic-release/semantic-release/discussions/3088

deps: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail

`v22.0.12`

Compare Source

Bug Fixes

Revert "fix(deps): update dependency cosmiconfig to v9" (#3104) (f6f1bf1)

`v22.0.11`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v9 (b38cd2e)

`v22.0.10`

Compare Source

Bug Fixes

revert updating cosmiconfig to v9 (88efead)

`v22.0.9`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v9 (#3072) (8b0dbd2)

`v22.0.8`

Compare Source

Bug Fixes

support windows absolute extends (#3062) (0d06f62)

`v22.0.7`

Compare Source

Bug Fixes

deps: update dependency read-pkg-up to v11 (#3047) (f09e55f)

Features

support extending ESM configuration files (#3036)(6900865)

`v22.0.6`

Compare Source

Bug Fixes

deps: update dependency figures to v6 (#3033) (305674d)

`v22.0.5`

Compare Source

Bug Fixes

deps: update dependency env-ci to v10 (#2983) (e759493)

`v22.0.4`

Compare Source

Bug Fixes

deps: update dependency marked to v9 (#2947) (84f2ee9)

`v22.0.3`

Compare Source

Bug Fixes

exports: removed the exports definition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.

`v22.0.2`

Compare Source

Bug Fixes

deps: update dependency marked-terminal to v6 (8a7befe)

`v22.0.1`

Compare Source

Bug Fixes

deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #2934

`v22.0.0`

Compare Source

Bug Fixes

deps: updated to the latest beta of the commit analyzer plugin (03a687b)
deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)

Features

conventional-changelog-presets: supported new preset format (07a79ea)
defined exports for the package (72ab317)
node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)

BREAKING CHANGES

node-versions: the minimum supported version for the v20 range of node has been raised slightly to
v20.6.1 to avoid a known node bug
node-versions: the minimum supported node version in the v20 major range is now v20.6
node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
exports prevents access to internal files, but they arent intended for public use anyway
conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

`v21.1.2`

Compare Source

Bug Fixes

deps: update dependency aggregate-error to v5 (#2956) (1017e1a)

`v21.1.1`

Compare Source

Bug Fixes

types: included the definitions file in the published package (#2920) (4c95c97)

`v21.1.0`

Compare Source

Features

Added TypeScript definitions (#2916) (c21a1ac)

`v21.0.9`

Compare Source

Bug Fixes

deps: update dependency hosted-git-info to v7 (#2908) (eba86ac)

`v21.0.8`

Compare Source

Bug Fixes

deps: update dependency execa to v8 (#2914) (7bc21fc)

`v21.0.7`

Compare Source

Bug Fixes

deps: update dependency read-pkg-up to v10 (#2862) (70996e0)

`v21.0.6`

Compare Source

Bug Fixes

get correct version if prerelease branch shares version with ... (#2416) (e4229f9)

`v21.0.5`

Compare Source

Bug Fixes

deps: update dependency marked to v5 (452e1fa)

`v21.0.4`

Compare Source

Bug Fixes

deps: update dependency @semantic-release/error to v4 (d259350)

`v21.0.3`

Compare Source

Bug Fixes

bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
bump @semantic-release/github to 9.0.0-beta.2 (#2818) (6f19d77)
deps: updated the beta plugins to stable versions (3941018)

`v21.0.2`

Compare Source

Bug Fixes

deps: update dependency @semantic-release/release-notes-generator to v11 (#2778) (ac40804)

`v21.0.1`

Compare Source

Bug Fixes

deps: update dependency env-ci to v9 (#2757) (4bddb37)

`v21.0.0`

Compare Source

BREAKING CHANGES

deps: the npm plugin has updated the npm dependency to v9
legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.

Bug Fixes

deps: bump @semantic-release/npm to ^10.0.0 (d647433)

`v20.1.3`

Compare Source

Bug Fixes

deps: update dependency execa to v7.1.1 (c38b53a)

`v20.1.2`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v8.1.2 (fbede54)

`v20.1.1`

Compare Source

Bug Fixes

deps: update dependency execa to v7 (#2709) (31d9bfe)

`v20.1.0`

Compare Source

Features

plugins: add support for loading ESM plugins (#2688) (d170f73)

`v20.0.4`

Compare Source

Bug Fixes

windows: fixed issues preventing execution from windows (#2672) (5df624c)

`v20.0.3`

Compare Source

Reverts

Revert "chore(deps): update dependency ava to v5.1.1" (#2682) (914b0a2), closes #2682

`v20.0.2`

Compare Source

Bug Fixes

deps: update dependency semver-diff to v4 (#1915) (cb45d27)

`v20.0.1`

Compare Source

Bug Fixes

deps: update dependency cosmiconfig to v8 (f914c1e)
deps: update dependency hosted-git-info to v6 (c4da008)

`v20.0.0`

Compare Source

BREAKING CHANGES

esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.

Features

esm: convert to esm (#2569) (9eab1ad), closes #2543
node-versions: raised the minimum required node version to v18 (#2620) (8a0d8be)

Bug Fixes

env-ci: updated to the stable esm-only version (#2632) (918eb59)
secrets-masking: used the proper named import from hook-std to enable masking for stderr (#2619) (cf6befa)

`v19.0.5`

Compare Source

Reverts

Revert "fix(deps): update dependency yargs to v17" (#2534) (8f07522), closes #2534 #2533

`v19.0.4`

Compare Source

Bug Fixes

deps: update dependency yargs to v17 (#1912) (f419080)

`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)

`v18.0.0`

Compare Source

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 workaroun

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e9bd0b7 to 4676972 Compare September 11, 2018 16:53

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4676972 to d2963fa Compare September 19, 2018 21:15

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d2963fa to 3cf74eb Compare October 4, 2018 06:06

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 0fe99be to 17b391c Compare October 20, 2018 16:48

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 91a297c to 5b14c5b Compare November 2, 2018 19:18

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c82910f to 3d67dc2 Compare November 12, 2018 20:23

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3d67dc2 to 497788a Compare November 14, 2018 16:36

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 266b9be to 8279986 Compare November 26, 2018 23:55

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d556ad4 to 0613388 Compare December 3, 2018 19:40

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 2dd2949 to 2e5260c Compare December 16, 2018 22:34

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2e5260c to 0b928ef Compare December 27, 2018 19:58

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0b928ef to 6fd5c39 Compare January 11, 2019 03:59

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6fd5c39 to 9aad2a6 Compare May 12, 2019 09:57

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9aad2a6 to d437e04 Compare June 19, 2019 11:51

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d437e04 to da51049 Compare July 13, 2019 12:00

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from da51049 to e087069 Compare August 10, 2019 12:00

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e087069 to cb4fca0 Compare August 20, 2019 05:49

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cb4fca0 to 0b425db Compare September 5, 2019 04:59

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0b425db to 06041d6 Compare November 11, 2019 06:59

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 06041d6 to 251b04e Compare November 21, 2019 13:55

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 251b04e to 633828e Compare December 22, 2019 05:57

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 633828e to c0fe88b Compare December 31, 2019 03:55

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ba6a7bf to 1c7e82d Compare June 2, 2023 22:33

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1c7e82d to 75a56b7 Compare June 10, 2023 01:33

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 75a56b7 to ae83546 Compare June 28, 2023 21:59

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 8e305d9 to bbefc9c Compare August 24, 2023 18:12

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f469624 to 74de66a Compare September 16, 2023 19:23

renovate bot changed the title ~~chore(deps): update dependency semantic-release to v21~~ chore(deps): update dependency semantic-release to v22 Sep 16, 2023

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 2762fb4 to d11fdde Compare September 24, 2023 19:57

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c4777ec to 5f28281 Compare November 3, 2023 22:14

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5f28281 to 0599c1a Compare November 17, 2023 03:04

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 68134c4 to 2e5de61 Compare December 12, 2023 01:04

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2e5de61 to e53074f Compare December 12, 2023 07:26

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e53074f to 9a10b87 Compare January 13, 2024 00:04

renovate bot changed the title ~~chore(deps): update dependency semantic-release to v22~~ chore(deps): update dependency semantic-release to v23 Jan 13, 2024

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c9c85b1 to ce10f52 Compare February 7, 2024 16:50

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from c2aa628 to de34cd3 Compare March 18, 2024 16:24

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from de34cd3 to 3c17503 Compare March 24, 2024 17:07

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3c17503 to caa89b9 Compare April 3, 2024 18:26

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

42abf12

renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from caa89b9 to 42abf12 Compare April 9, 2024 22:12

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency semantic-release to v23 #54

chore(deps): update dependency semantic-release to v23 #54

renovate bot commented Sep 9, 2018 •

edited

chore(deps): update dependency semantic-release to v23 #54

Are you sure you want to change the base?

chore(deps): update dependency semantic-release to v23 #54

Conversation

renovate bot commented Sep 9, 2018 • edited

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Reverts

Bug Fixes

Bug Fixes

BREAKING CHANGES

Features

Bug Fixes

Reverts

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

renovate bot commented Sep 9, 2018 •

edited