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.

Sign up for GitHub

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

Jump to bottom

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

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

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 9.0.2 -> 13.0.0 age adoption passing confidence
@semantic-release/github 8.1.0 -> 11.0.1 age adoption passing confidence
@semantic-release/npm 9.0.2 -> 12.0.1 age adoption passing confidence
@semantic-release/release-notes-generator 10.0.3 -> 14.0.1 age adoption passing confidence
semantic-release 19.0.5 -> 24.2.0 age adoption passing confidence

Release Notes

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

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

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

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

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

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
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.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

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

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

v24.1.1

Compare Source

v24.1.0

Compare Source

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

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)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

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 6 times, most recently from 2408be4 to b789856 Compare January 14, 2023 10:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 174dac6 to 5d7d385 Compare January 23, 2023 04:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from edc7e22 to 8de6b10 Compare January 30, 2023 03:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 363846a to eabd10b Compare February 8, 2023 10:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 130f66e to 3937d44 Compare February 23, 2023 16:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 10 times, most recently from 621872d to 5c19cc3 Compare March 3, 2023 09:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 2d25980 to c08e3db Compare March 13, 2023 10:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 8996b04 to 3cd6db6 Compare March 21, 2023 01:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 95d98f8 to 7dff721 Compare May 22, 2024 19:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 3748f10 to 810501a Compare June 5, 2024 04:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 810501a to f5b12f0 Compare June 22, 2024 05:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 593eb6e to aa8b7b5 Compare July 8, 2024 14:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 94804c6 to f939189 Compare July 9, 2024 08:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 7bbdf12 to 0eb8f09 Compare July 26, 2024 03:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ff948c9 to baf13d1 Compare August 15, 2024 19:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 76420b3 to 0b02d7e Compare August 20, 2024 22:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 92e5c01 to 032fe2f Compare September 6, 2024 00:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 616e6c3 to e803a45 Compare September 15, 2024 15:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 72d544d to db302b1 Compare September 27, 2024 19:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b3daa9f to 325f384 Compare October 25, 2024 22:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 325f384 to 59217fa Compare November 7, 2024 02:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants