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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 12, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 11.1.0 -> 13.0.0 age adoption passing confidence
@semantic-release/github 9.2.6 -> 11.0.1 age adoption passing confidence
@semantic-release/npm 11.0.3 -> 12.0.1 age adoption passing confidence
@semantic-release/release-notes-generator 12.1.0 -> 14.0.1 age adoption passing confidence
semantic-release 22.0.12 -> 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
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
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
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
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

v23.0.1

Compare Source

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

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

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


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 3 times, most recently from 6d42b17 to 79d6f02 Compare January 17, 2024 05:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 48136f9 to e9fcfe6 Compare January 31, 2024 12:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 1effe48 to 32cf4c6 Compare February 8, 2024 18:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 635d7cd to ae22562 Compare February 24, 2024 00:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ae22562 to 7680005 Compare March 15, 2024 00:14
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update semantic-release monorepo (major) Mar 15, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 4935c0d to ae8f8dc Compare March 18, 2024 14:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c02eb7b to 9418c38 Compare March 24, 2024 17:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from b183548 to 8f9447c Compare April 4, 2024 07:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f92600a to b066f1a Compare June 22, 2024 07:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 5e66413 to b483163 Compare July 8, 2024 14:34
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ef78114 to 61b3634 Compare July 26, 2024 03:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from dadf6d5 to cb1326c Compare August 15, 2024 18:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e9f9dfb to cc80340 Compare August 20, 2024 21:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 4e2e228 to dcee84a Compare August 26, 2024 06:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 3694623 to 23c0b76 Compare September 6, 2024 01:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from cae8ce2 to 56b2eac Compare September 15, 2024 15:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 85fa78f to a71f41d Compare September 27, 2024 18:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 992b205 to 2bdab70 Compare October 25, 2024 22:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2bdab70 to cb22324 Compare November 6, 2024 20:15
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