Skip to content

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

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

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 14, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 11.1.0 -> 13.0.1 age adoption passing confidence
@semantic-release/exec 6.0.3 -> 7.0.3 age adoption passing confidence
@semantic-release/github 9.2.6 -> 11.0.2 age adoption passing confidence
@semantic-release/release-notes-generator 12.1.0 -> 14.0.3 age adoption passing confidence
semantic-release 22.0.12 -> 24.2.3 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/exec (@​semantic-release/exec)

v7.0.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

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

v11.0.2

Compare Source

Bug Fixes

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

Bug Fixes
  • glob-assets: remove unnecessary option when invoking globby() (#​924) (efe9f49)

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

Bug Fixes
  • edge-case: fetching associatedPRs on 100+ context.commits in success lifecycle (#​892) (dfe47e9)

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

Bug Fixes

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

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

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

Bug Fixes

v24.1.0

Compare Source

Features

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

Bug Fixes

v23.1.0

Compare Source

Features

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

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

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 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 added the renovate label Jan 14, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fc6a295 to dedba5d Compare February 7, 2024 15:49
@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 9f536b4 to bbb42b1 Compare March 18, 2024 16:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fcdbba2 to 99dca7d Compare March 24, 2024 19:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 23fd4ee to eb59d04 Compare April 9, 2024 21:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from c06d13d to 36ae7ed Compare May 15, 2024 23:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 36ae7ed to 297978d Compare May 22, 2024 20:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 90cc494 to 1ab570b Compare June 5, 2024 04:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1ab570b to 1f1e8de Compare June 22, 2024 04:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3527311 to f9637df Compare July 8, 2024 16:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ec484b7 to 457963e Compare July 26, 2024 01:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from b1b0a05 to 0d596bb Compare August 15, 2024 18:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fb0b6f5 to 106ea64 Compare August 20, 2024 21:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from c222507 to 545abf6 Compare September 6, 2024 01:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from a270f6a to 1b3b721 Compare September 15, 2024 15:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from f6d069f to f39a0ae Compare September 27, 2024 17:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b6b7fd4 to 8d46031 Compare October 25, 2024 22:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8d46031 to 34ecd90 Compare November 6, 2024 20:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 34ecd90 to d222993 Compare December 16, 2024 20:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d222993 to 59b25f4 Compare January 3, 2025 04:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 923d1c2 to 5949b9d Compare February 3, 2025 04:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0b832b7 to 5d4a61e Compare February 15, 2025 22:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5d4a61e to 3e248d3 Compare April 25, 2025 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant