Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 30, 2024

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/github 10.3.312.0.5 age confidence
@semantic-release/npm 12.0.113.1.4 age confidence
semantic-release 24.1.125.0.3 age confidence

Release Notes

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

v12.0.5

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release POST request during publish (#​1157) (38051ba)

v12.0.4

Compare Source

Bug Fixes

v12.0.3

Compare Source

Bug Fixes
  • extend GraphQL alias prefix to prevent hash collisions (#​1134) (ea6386d)

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

v13.1.4

Compare Source

Bug Fixes

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

v25.0.3

Compare Source

Bug Fixes

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

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 from 49120ef to 3f1812e Compare November 7, 2024 06:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3f1812e to 3385aa9 Compare April 26, 2025 15:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3385aa9 to 51e1559 Compare May 31, 2025 04:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 51e1559 to 857d76d Compare August 14, 2025 23:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 857d76d to 7246e54 Compare September 1, 2025 14:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7246e54 to fea2a1c Compare September 11, 2025 15:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fea2a1c to e6b22fd Compare September 26, 2025 08:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e6b22fd to 7570906 Compare October 13, 2025 23:04
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/github to v11 chore(deps): update semantic-release monorepo (major) Oct 13, 2025
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 559da09 to 539b3a4 Compare October 21, 2025 03:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 539b3a4 to d5bd01d Compare October 25, 2025 19:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 608457c to eb56347 Compare November 8, 2025 20:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ae0a90a to 76fce68 Compare November 19, 2025 04:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 76fce68 to 9acdb19 Compare December 5, 2025 11:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9acdb19 to 80352c2 Compare December 13, 2025 20:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 80352c2 to 5e3deff Compare January 1, 2026 03:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5e3deff to dd4ec18 Compare January 8, 2026 23:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 26be1c7 to 9ac1920 Compare January 24, 2026 07:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 251b538 to 5d89136 Compare February 3, 2026 23:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5d89136 to f10a379 Compare February 7, 2026 08:01
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