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

build(deps): update semantic-release (major) #459

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 14, 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.0 -> ~11.0.0 age adoption passing confidence
@semantic-release/npm ~11.0.0 -> ~12.0.0 age adoption passing confidence
@semantic-release/release-notes-generator ~12.1.0 -> ~14.0.0 age adoption passing confidence

Release Notes

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
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.3

Compare Source

Bug Fixes

v14.0.2

Compare Source

Bug Fixes

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

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 requested a review from wopian March 14, 2024 22:57
@renovate renovate bot changed the title build(deps): update devdependency @semantic-release/github to ~10.0.0 build(deps): update semantic-release (major) Mar 16, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 5 times, most recently from 4173e78 to 5d358e0 Compare March 21, 2024 02:02
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 5 times, most recently from b53092e to ac18e48 Compare March 30, 2024 09:08
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 857b253 to 596357b Compare April 8, 2024 01:43
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from d9d7957 to d19a7bf Compare April 22, 2024 04:31
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 6 times, most recently from 5ad8f0d to 1b2718d Compare May 6, 2024 00:08
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 4 times, most recently from e2ca98b to 8d87b00 Compare May 13, 2024 05:00
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 0730d54 to e6561bc Compare May 27, 2024 05:07
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from cdddf2c to ac0a39c Compare October 7, 2024 03:59
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from f8a14a1 to 8062f79 Compare October 21, 2024 03:05
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from 60f4ea5 to 9231b44 Compare October 28, 2024 03:38
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from d373f69 to a2d4301 Compare November 5, 2024 06:13
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 85b6828 to 680eca3 Compare November 18, 2024 04:55
Copy link

github-actions bot commented Nov 18, 2024

yarn.lock changes

Click to toggle table visibility
Name Status Previous Current
@semantic-release/commit-analyzer UPDATED 12.0.0 13.0.1
@semantic-release/github UPDATED 10.3.5 11.0.1
@semantic-release/release-notes-generator UPDATED 13.0.0 14.0.3
conventional-changelog-angular UPDATED 7.0.0 8.0.0
conventional-changelog-writer UPDATED 7.0.1 8.0.1
conventional-commits-filter UPDATED 4.0.0 5.0.0
conventional-commits-parser UPDATED 5.0.0 6.1.0
deprecation REMOVED 2.3.1 -
import-from-esm UPDATED 1.3.4 2.0.0
meow UPDATED 12.1.1 13.2.0

@renovate renovate bot force-pushed the renovate/major-semantic-release branch 6 times, most recently from ff8662e to ac18476 Compare November 26, 2024 10:04
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from ac18476 to a8c8082 Compare December 2, 2024 04:01
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 769762b to 3a741f8 Compare December 16, 2024 03:28
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 75a44b9 to 18124cc Compare December 23, 2024 05:17
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 2d69d56 to 122399d Compare December 30, 2024 04:58
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 122399d to f209dfd Compare January 8, 2025 01:37
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from f209dfd to aae7bcd Compare February 1, 2025 04:58
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from aae7bcd to 9e2a54e Compare March 1, 2025 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant