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

fix(deps): update semantic-release monorepo (major) #41

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

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github 7.2.3 -> 9.2.1 age adoption passing confidence
@semantic-release/npm 9.0.2 -> 11.0.0 age adoption passing confidence
semantic-release 19.0.5 -> 22.0.5 age adoption passing confidence

Release Notes

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

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

v11.0.0

Compare Source

Bug Fixes
  • deps: update dependency npm to v10 (819f257)
Features
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)
BREAKING CHANGES
  • node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

v10.0.6

Compare Source

Bug Fixes

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes

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

Bug Fixes
  • aggregate-error: upgraded to the latest version (7285e05)
  • deps: upgraded npm to v9 (2a79f80)
  • execa: upgraded to the latest version (7c74660)
  • normalize-url: upgraded to the latest version (b55bb01)
  • remove support for legacy auth (51ab3c8)
  • tempy: upgraded to the latest version of tempy (f1992a5)
Code Refactoring
  • esm: converted the package to esm (2d8ff15)
Features
  • node-versions: dropped support for node versions below v18 (aff3574)
  • semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)
BREAKING CHANGES
  • deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
    can be found at https://github.com/npm/cli/releases/tag/v9.0.0
  • semantic-release-peer: the required version of semantic-release has been
    raised to v20.1.0 in order to support loading of ESM plugins
  • aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
  • node-versions: node v18 is now the minimum required node version
  • esm: @semantic-release/npm is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare,
    publish, addChannel)
semantic-release/semantic-release (semantic-release)

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes
  • exports: removed the exports definition for the time being (561e2d6), closes #​2968

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

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

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

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

v21.0.1

Compare Source

Bug Fixes

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

v20.1.0

Compare Source

Features

v20.0.4

Compare Source

Bug Fixes
  • windows: fixed issues preventing execution from windows (#​2672) (5df624c)

v20.0.3

Compare Source

Reverts

v20.0.2

Compare Source

Bug Fixes

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

Configuration

📅 Schedule: Branch creation - "before 7am every weekday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1b00fad to 1670349 Compare September 23, 2021 03:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0016110 to 940e937 Compare October 21, 2021 04:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d0909dd to cbdd147 Compare November 4, 2021 05:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cbdd147 to 12227ac Compare November 24, 2021 09:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 12227ac to b6010eb Compare January 18, 2022 09:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 16 times, most recently from 54ccf32 to 2131957 Compare February 7, 2022 03:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2131957 to 29494a3 Compare February 28, 2022 22:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 29494a3 to 0db2f22 Compare March 29, 2022 16:21
@renovate renovate bot changed the title fix(deps): update semantic-release monorepo (major) fix(deps): update dependency @semantic-release/github to v8 Jun 2, 2022
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 5aa4177 to 2840eca Compare June 3, 2022 02:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from dd43b8a to 2ca1943 Compare July 8, 2022 03:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 0283a1d to d13e57c Compare June 3, 2023 21:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 9c4eb34 to 3b29e88 Compare June 10, 2023 01:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1dab709 to aefdbb3 Compare July 5, 2023 02:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from aefdbb3 to 1f5f007 Compare July 16, 2023 03:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1f5f007 to 98ddcf8 Compare August 19, 2023 16:15
@renovate
Copy link
Contributor Author

renovate bot commented Aug 19, 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 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 could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   semantic-release@"22.0.5" from the root project
npm ERR!   peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/github
npm ERR!     @semantic-release/github@"9.2.1" from the root project
npm ERR!     @semantic-release/github@"^9.0.0" from [email protected]
npm ERR!   3 more (@semantic-release/npm, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=11.0.0 <16.0.0" from [email protected]
npm ERR! node_modules/semantic-release-docker
npm ERR!   semantic-release-docker@"2.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=11.0.0 <16.0.0" from [email protected]
npm ERR!   node_modules/semantic-release-docker
npm ERR!     semantic-release-docker@"2.2.0" 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/worker/f78096/13eebe/cache/others/npm/_logs/2023-09-28T01_28_07_675Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/f78096/13eebe/cache/others/npm/_logs/2023-09-28T01_28_07_675Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 09290a1 to 1e7bda3 Compare August 24, 2023 18:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 3576a65 to eb8bf5d Compare September 16, 2023 06:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 566c3b1 to 35df748 Compare September 23, 2023 13:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from aa8f6e7 to b061f12 Compare September 27, 2023 01:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b061f12 to 1183aaf Compare September 28, 2023 01:28
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