Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 5.0.1 -> 6.0.3 age adoption passing confidence
@semantic-release/commit-analyzer 8.0.1 -> 13.0.0 age adoption passing confidence
@semantic-release/exec 5.0.0 -> 6.0.3 age adoption passing confidence
@semantic-release/git 9.0.1 -> 10.0.1 age adoption passing confidence
@semantic-release/release-notes-generator 9.0.3 -> 14.0.1 age adoption passing 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
semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

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
semantic-release/exec (@​semantic-release/exec)

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 (#​188) (020eab0)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17
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
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
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

v13.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (5655b18)
  • node-versions: dropped support for node v18 and v19 (e65959a)
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

v12.1.0

Compare Source

Features

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Bug Fixes
  • deps: update dependency conventional-changlog-writer to v7 (4fe3563)
Features
  • conventional-changelog-presets: supported new preset format (a681671)
  • node-versions: raised the minimum node version to v18.17 and dropped v19 support (9c4e5f5)
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

v11.0.7

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-filter to v4 (a347fa6)

v11.0.6

Compare Source

Reverts
  • Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#​509)" (e6b939a), closes #​509
  • Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#​511)" (1f6fa69), closes #​511
  • Revert "chore(deps): update dependency conventional-changelog-conventionalcommits to v7 (#​510)" (9793686), closes #​510
  • Revert "chore(deps): update dependency conventional-changelog-eslint to v5 (#​512)" (a74f93d), closes #​512
  • Revert "chore(deps): update dependency conventional-changelog-express to v4 (#​513)" (a84e7ed), closes #​513

v11.0.5

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (#​508) (45f893f)

v11.0.4

Compare Source

Bug Fixes
  • deps: update dependency read-pkg-up to v10 (68772c4)

v11.0.3

Compare Source

Bug Fixes
  • deps: update dependency conventional-changelog-angular to v6 (#​466) (a8d8868)
  • deps: update dependency conventional-changelog-writer to v6 (#​467) (d80b880)
  • deps: update dependency conventional-commits-filter to v3 (#​468) (b058ee7)
  • deps: update dependency conventional-commits-parser to v4 (#​469) (7d84222)

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes
  • files: include the wrappers directory in the published package (949607f)

v11.0.0

Compare Source

Code Refactoring
Features
  • node-versions: raised the minimum required node version to v18 (4bfe425)
  • semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (f094cb0)
BREAKING CHANGES
  • semantic-release-peer: the required version of semantic-release has been raised to v20.1.0 in order to support loading of ESM plugins
  • node-versions: node v18 is now the minimum supported version
  • esm: @semantic-release/release-notes-generator is now a native ES Module. It has
    named exports for each plugin hook (generateNotes)

v10.0.3

Compare Source

Bug Fixes
  • bump conventional commits parser to version 3.2.3 (#​293) (5f9d65d)

v10.0.2

Compare Source

Bug Fixes
  • deps: update dependency conventional-changelog-writer to v5 (#​212) (6724eca)

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

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

@​abel-mak


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 is behind base branch, 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 7 times, most recently from 6877bd9 to 1ecf0eb Compare September 22, 2021 01:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from a90a9d9 to b6cfc59 Compare October 3, 2021 17:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 58c535d to f6eac66 Compare October 10, 2021 18:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f6eac66 to 6fda77a Compare October 11, 2021 02:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 020a4dc to f8a67a9 Compare October 25, 2021 21:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1821586 to dab6c8a Compare October 31, 2021 18:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dab6c8a to 027bda4 Compare November 7, 2021 18:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 7fab592 to 21dd198 Compare November 21, 2021 18:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from b17d109 to bcdb687 Compare November 28, 2021 16:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3949ca5 to 7671111 Compare December 12, 2021 18:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0ef8798 to 49cd520 Compare June 18, 2022 14:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 49cd520 to 75def97 Compare September 25, 2022 19:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 75def97 to a8d7da0 Compare March 17, 2023 18:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8b9ac89 to 85e70f4 Compare March 24, 2023 21:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 7fd6764 to 6a2fc2a Compare June 2, 2023 20:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6a2fc2a to e3c3810 Compare June 7, 2023 18:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e3c3810 to b5d7492 Compare July 4, 2023 18:40
@renovate
Copy link
Contributor Author

renovate bot commented Aug 24, 2023

⚠ 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 click 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"17.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR! node_modules/@semantic-release/changelog
npm ERR!   dev @semantic-release/changelog@"6.0.3" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-24T08_02_22_019Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-24T08_02_22_019Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 7 times, most recently from 6387301 to d39199e Compare August 28, 2023 21:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d39199e to 1309f98 Compare September 18, 2023 13:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 73ab9cd to b4c4914 Compare October 4, 2023 22:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from a53215d to 55b8b87 Compare November 6, 2023 04:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 55b8b87 to 05fa438 Compare January 25, 2024 06:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4372b7f to 23c056e Compare March 24, 2024 08:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 23c056e to 0f10a05 Compare June 1, 2024 01:39
Copy link
Contributor Author

renovate bot commented Jun 1, 2024

⚠️ 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 click 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/semantic-release
npm error   dev semantic-release@"17.4.7" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm error node_modules/@semantic-release/changelog
npm error   dev @semantic-release/changelog@"6.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-22T08_10_24_328Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-22T08_10_24_328Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0f10a05 to 0c3e8c1 Compare June 22, 2024 08:10
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.

1 participant