Skip to content

Comments

chore(deps): update semantic-release monorepo (major)#7

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-semantic-release-monorepo
Open

chore(deps): update semantic-release monorepo (major)#7
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-semantic-release-monorepo

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 9, 2020

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog 3.0.56.0.3 age confidence
@semantic-release/commit-analyzer 6.3.113.0.1 age confidence
@semantic-release/git 7.0.1710.0.1 age confidence
@semantic-release/github 5.5.512.0.6 age confidence
@semantic-release/npm 5.3.213.1.4 age confidence

Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (#​170) (5cf74e4)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v5.0.1

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore
  • require Node.js >=10.18 (5ffdf49)
BREAKING CHANGES
  • Require Node.js >= 10.18

v4.0.0

Compare Source

Features
  • require Node.js >=10.13 (1f483af)
BREAKING CHANGES
  • Require Node.js >= 10.13

v3.0.6

Compare Source

Bug Fixes
  • use correct peerDependencies for semantic-release (d36ee06)
semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are
    dropping support for previous major versions of those packages due to the breaking changes between
    majors. this only impacts your project if you are installing alongside semantic-release, so updating
    those packages to latest version should be the only change you need for this update. no action
    should be necessary if you are using default semantic-release config

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (f3358dd)
  • node-versions: dropped support for node v18 and v19 (0a23b82)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.1.0

Compare Source

Features

v11.0.0

Compare Source

Bug Fixes
  • config-loader: accounted for normalization of preset interfaces (3ff9458)
  • deps: update dependency conventional-commits-filter to v4 (99dcf7e)
Features
  • conventional-changelog-presets: supported new preset format (f3b88d3)
  • node-versions: raised the minimum node version to v18.17 and dropped v19 support (a681fbd)
BREAKING CHANGES
  • node-versions: the minimum required node version is now v18.17, v19 support has been dropped, and the minimum required in the v20 range is v20.6.1
  • 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

v10.0.4

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (a7201b6)

v10.0.3

Compare Source

Reverts
  • Revert "fix(deps): update dependency conventional-commits-parser to v5 (#​501)" (ab3ee9f), closes #​501
  • Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#​502)" (f21eb8e), closes #​502
  • Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#​504)" (c48b533), closes #​504

v10.0.2

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (#​501) (91cf4d5)

v10.0.1

Compare Source

Bug Fixes
  • deps: update dependency conventional-changelog-angular to v6 (#​460) (0607201)
  • deps: update dependency conventional-commits-filter to v3 (#​461) (97d683f)
  • deps: update dependency conventional-commits-parser to v4 (#​462) (5d94efa)

v10.0.0

Compare Source

Code Refactoring
Features
  • deps: raised the peer-dependency requirement on semantic-release to v20.1.0 (e1ab8ea)
  • node-versions: raised the minimum required node version to v18 (affeb23)
BREAKING CHANGES
  • deps: the minimum required version of semantic-release is now v20.1.0 in order to support
    loading ESM plugins
  • node-versions: the minimum required version of node is now v18
  • esm: @semantic-release/commit-analyzer is now a native ES Module. It has named exports
    for each plugin hook (analyzeCommits)

v9.0.2

Compare Source

Bug Fixes
  • bump conventional commits parser to version 3.2.3 (#​289) (fc0a88a)

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of node is now v14.17

v8.0.1

Compare Source

Bug Fixes
  • package: update micromatch to version 4.0.2 (ab3e4fd)

v8.0.0

Compare Source

chore
  • require Node.js >=10.18 (3f1dfc3)
BREAKING CHANGES
  • Require Node.js >= 10.18

v7.0.0

Compare Source

Bug Fixes
  • use correct peerDependencies for semantic-release (4ff652f)
  • package: update import-from to version 3.0.0 (060dc29)
Features
  • add support for conventionalcommits preset (2b5ac0a)
  • allow to disable default release rules with release: false (ea2b204)
  • require Node.js >=10.13 (9f72907)
  • use globs instead of regexp for releases rules (fc9b28a)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • 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-*'.

v6.3.3

Compare Source

Bug Fixes
  • package: update conventional-commits-parser to version 3.0.7 (4a929ca)

v6.3.2

Compare Source

Bug Fixes
  • ignore empty commit messages (595c81f)
semantic-release/git (@​semantic-release/git)

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (7ab65f8)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

chore
  • require Node.js >=10.18 (4016fcc)
BREAKING CHANGES
  • Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (9c1dc67)
  • include deleted files in release commit (f59d20c)
  • package: update aggregate-error to version 2.0.0 (3eb8f60)
  • package: update execa to version 2.0.2 (9404d44)
  • package: update execa to version 3.0.0 (e6af5b4)
  • look for modified fiels to commit only if there files matching the globs (d97c030)
  • update globby to latest version (9e2b2e5)
Features
  • require Node.js >=10.13 (81955b8)
  • require Node.js >=8.15 (15356b1)
  • support branch parameter from semantic-release@​16.0.0 (02b1f6d)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15

v7.0.18

Compare Source

Bug Fixes
  • use correct debug scope (3323aac)
semantic-release/github (@​semantic-release/github)

v12.0.6

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release PATCH request during publish (#​1169) (f516337)

v12.0.5

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release POST request during publish (#​1157) (38051ba)

v12.0.4

Compare Source

Bug Fixes

v12.0.3

Compare Source

Bug Fixes
  • extend GraphQL alias prefix to prevent hash collisions (#​1134) (ea6386d)

v12.0.2

Compare Source

Bug Fixes
  • add undici ProxyAgent support for GitHub Enterprise Server behind proxies (#​1104) (15def77)

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

Bug Fixes
  • glob-assets: remove unnecessary option when invoking globby() (#​924) (efe9f49)

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

Bug Fixes
  • edge-case: fetching associatedPRs on 100+ context.commits in success lifecycle (#​892) (dfe47e9)

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

Bug Fixes

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported

v9.2.6

Compare Source

Bug Fixes

v9.2.5

Compare Source

Bug Fixes

v9.2.4

Compare Source

Bug Fixes

v9.2.3

Compare Source

Bug Fixes

v9.2.2

Compare Source

Bug Fixes

v9.2.1

Compare Source

v9.2.0

Compare Source

Features

v9.1.0

Compare Source

Features
  • releaseNameTemplate and releaseBodyTemplate options for customizing release body and name (#​704) (9e2678c)

v9.0.7

Compare Source

Bug Fixes

v9.0.6

Compare Source

Bug Fixes

v9.0.5

Compare Source

Bug Fixes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

BREAKING CHANGES
  • @semantic-release/github is now a native ES Module
  • Node 14 and 16 are no longer supported

v8.1.0

Compare Source

Features

v8.0.9

Compare Source

Bug Fixes

v8.0.8

Compare Source

Bug Fixes
  • Use Octokit for request retries and throttling to prevent rate limit errors (#​487) (3dc59ec)

v8.0.7

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (8bba5f0)

v8.0.6

Compare Source

Bug Fixes

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Bug Fixes
  • revert "fix(deps): update dependency url-join to v5" (6e4dfca)

v8.0.3

Compare Source

Bug Fixes
  • deps: update dependency url-join to v5 (7725391)

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

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

v7.2.3

Compare Source

Bug Fixes

v7.2.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (1a28625)

v7.2.1

Compare Source

Bug Fixes
  • allow proxy to be false and fallback an empty string (#​356) (bea917f)

v7.2.0

Compare Source

Features

v7.1.2

Compare Source

Bug Fixes

v7.1.1

Compare Source

Bug Fixes

v7.1.0

Compare Source

Features
  • add additional release links to the release (#​282) ([db2e9c8](https

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from aba9282 to a593314 Compare January 9, 2020 20:00
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/git to v8 chore(deps): update semantic-release monorepo (major) Jan 9, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 0ea5ec1 to d3e0a81 Compare January 10, 2020 17:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d3e0a81 to 9e9db42 Compare January 18, 2020 19:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9e9db42 to fd4d83d Compare February 8, 2020 14:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fd4d83d to 16b1d3c Compare February 20, 2020 13:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 16b1d3c to 0314755 Compare March 14, 2020 06:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0314755 to b80ee00 Compare May 3, 2020 14:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b80ee00 to 2feaeeb Compare May 15, 2020 10:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2feaeeb to 33a9102 Compare July 1, 2020 14:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 33a9102 to 5504e04 Compare April 26, 2021 13:29
@renovate
Copy link
Author

renovate bot commented Apr 26, 2021

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you check the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @barajs/loader@1.0.0
npm ERR! Found: semantic-release@15.13.28
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"15.13.28" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/commit-analyzer@8.0.1
npm ERR! node_modules/@semantic-release/commit-analyzer
npm ERR!   dev @semantic-release/commit-analyzer@"8.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-04-26T13_29_04_133Z-debug.log

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5504e04 to c6ef6ea Compare May 9, 2021 22:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c6ef6ea to 0812986 Compare October 18, 2021 20:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0812986 to 70b2712 Compare March 7, 2022 16:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 70b2712 to 8640c27 Compare April 25, 2022 00:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8640c27 to ec49f30 Compare September 25, 2022 15:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ec49f30 to dcc4c54 Compare November 20, 2022 15:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dcc4c54 to 73f132b Compare March 17, 2023 08:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 73f132b to c9beb0a Compare March 24, 2023 20:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from a9cc4ec to d52ec14 Compare June 4, 2023 08:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d52ec14 to 5649fc2 Compare June 10, 2023 05:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5649fc2 to 7b2f5b1 Compare July 16, 2023 04:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7b2f5b1 to 64592d2 Compare August 20, 2023 02:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 64592d2 to 296bda4 Compare August 27, 2023 20:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a7d602e to 884137f Compare January 3, 2025 20:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 884137f to 7a74038 Compare April 26, 2025 19:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7a74038 to 1349872 Compare May 26, 2025 19:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1349872 to 2fe2bc6 Compare June 29, 2025 04:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 418fea3 to dd01797 Compare August 15, 2025 11:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dd01797 to 991e0d3 Compare August 23, 2025 12:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 991e0d3 to cfcbe24 Compare September 1, 2025 07:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cfcbe24 to 781e709 Compare September 14, 2025 19:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 781e709 to 15ad102 Compare September 26, 2025 20:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 0db4555 to 8a53996 Compare October 20, 2025 20:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8a53996 to 30f4591 Compare October 23, 2025 16:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 30f4591 to a6597cc Compare November 2, 2025 03:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 97ce6a7 to 5d862aa Compare November 16, 2025 20:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5d862aa to d1232e3 Compare November 19, 2025 15:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d1232e3 to 4cbfaef Compare December 3, 2025 23:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4cbfaef to e135944 Compare December 13, 2025 07:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e135944 to fcaeca0 Compare January 1, 2026 02:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fcaeca0 to 1dbf5e4 Compare January 9, 2026 03:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from bc71344 to 51a7e07 Compare January 24, 2026 19:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 116afcb to acaaf6b Compare February 3, 2026 04:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 98a3557 to e5937ed Compare February 13, 2026 16:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e5937ed to eb3c98d Compare February 18, 2026 03:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants