Skip to content

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

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
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

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

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/github ^8.0.7 → ^12.0.0 age confidence
@semantic-release/npm ^9.0.1 → ^13.0.0 age confidence
semantic-release ^19.0.5 → ^25.0.0 age confidence

Release Notes

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

v12.0.2

Compare Source

Bug Fixes
  • add undici ProxyAgent support for GitHub Enterprise Server behind proxies (#​1104) (15def77)

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

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

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

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

v13.1.3

Compare Source

Bug Fixes

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • publish-dry-run: temporarily remove the addition of dry-running the publish step (30bd176)

v13.1.0

Compare Source

Features
  • trusted-publishing: verify auth, considering OIDC vs tokens from various registries (e3319f1), closes #​958
  • trusted-publishing: refine the messages for related errors (316ce21), closes #​958
  • trusted-publishing: make request to verify if OIDC token exchange can succeed (c80ecb0), closes #​958
  • trusted-publishing: pass id-token as bearer header for github actions (d83b727), closes #​958
  • trusted-publishing: pass id-token as bearer header for gitlab pipelines (6d1c3cf), closes #​958
  • trusted-publishing: handle failure to retrieve id-token in the context of github actions (b673257), closes #​958
  • auth-error: update messaging for auth failure to be less token specific (e24967d)
  • auth: attempt a dry-run publish to determine auth status (841dc67)
Bug Fixes
  • trusted-publishing: uri encode the package name for the token exchange request (3dd95d0), closes #​958
  • auth: throw appropriate error when auth context fails to enable publishing (f5c8d85)
  • auth: throw error if dry-run publish determines lack of auth (8f88e9d)
  • verify-auth: enable the publish dry-run to work for projects publishing from a sub-directory (e7d684c)

v13.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23
  • node-versions: raise the minimum node version requirement for the v24 range (935439e)
Bug Fixes
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • deps: a minimum of node v22.14 is now required

v12.0.2

Compare Source

Bug Fixes

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)

v9.0.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (7157d76)
  • deps: update dependency npm to v9 (28265ec)
  • deps: update dependency registry-auth-token to v5 (187671f)
  • revert): "fix(deps: update dependency npm to v9" (#​561) (c28a848)
semantic-release/semantic-release (semantic-release)

v25.0.2

Compare Source

Bug Fixes

v25.0.1

Compare Source

Bug Fixes

v25.0.0

Compare Source

Bug Fixes
  • deps: update dependency hosted-git-info to v9 (9fa04f8)
  • deps: update dependency yargs to v18 (#​3745) (cde9a72)
  • deps: update to the stable version of the github plugin (f12cf81)
  • deps: update to the stable version of the release-notes-generator plugin (d9def72)
  • deps: updated to the stable version of the commit-analyzer plugin (291533b)
  • deps: upgrade to the new major version of the npm plugin, which upgrades npm to v11 for publishing (1be8290)
Features
  • node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
  • node-versions: raise the minimum node version for the v24 range (116a188)
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • node-versions: a minimum of node v22.14 is now required

v24.2.9

Compare Source

Bug Fixes

v24.2.8

Compare Source

Bug Fixes

v24.2.7

Compare Source

Performance Improvements

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

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

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.

@changeset-bot
Copy link

changeset-bot bot commented Jan 6, 2023 •
edited
Loading

⚠️ No Changeset found

Latest commit: bae6b38

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v20 chore(deps): update semantic-release monorepo (major) Mar 22, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4762ffe to 616ccde Compare March 24, 2023 20:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 616ccde to 4ce6bbe Compare June 2, 2023 20:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4ce6bbe to 7e74fe7 Compare July 1, 2023 04:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7e74fe7 to c1cc14a Compare July 28, 2023 16:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3d2d99e to 93d968a Compare September 16, 2023 20:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 93d968a to 3340699 Compare October 17, 2023 14:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3340699 to 729fd82 Compare January 13, 2024 02:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 844e5ba to 375a056 Compare March 16, 2024 04:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 375a056 to fdfcd71 Compare May 31, 2024 22:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fdfcd71 to 6e92f12 Compare September 24, 2024 21:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ddf224c to f4c9f59 Compare August 13, 2025 15:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f4c9f59 to 617a0c6 Compare August 19, 2025 18:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 617a0c6 to 139be04 Compare August 31, 2025 09:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 4d94f7d to c25a2cf Compare September 25, 2025 16:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from f64f985 to 9557d63 Compare October 19, 2025 21:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9557d63 to 458b5f9 Compare October 21, 2025 16:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 458b5f9 to b607787 Compare November 1, 2025 02:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from e09941c to 909049f Compare November 10, 2025 23:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 6a7ec58 to 80b5c33 Compare November 18, 2025 22:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 80b5c33 to f8185d7 Compare December 3, 2025 19:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f8185d7 to 5d859af Compare December 12, 2025 23:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5d859af to d0d8681 Compare December 31, 2025 15:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d0d8681 to bae6b38 Compare January 8, 2026 18:52
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.

1 participant