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 dependency semantic-release to v23 #206

Merged
merged 1 commit into from
Feb 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 21.0.6 -> 23.0.2 age adoption passing confidence

Release Notes

semantic-release/semantic-release (semantic-release)

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

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@coveralls
Copy link

coveralls commented Oct 1, 2023

Coverage Status

coverage: 97.573% (-0.03%) from 97.603%
when pulling 423b1c4 on renovate/major-semantic-release-monorepo
into db1f199 on master.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 7863524 to b90dd1c Compare November 4, 2023 09:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b90dd1c to c674e2c Compare November 17, 2023 03:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 0c22799 to 6137a51 Compare December 12, 2023 01:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6137a51 to 3e329a6 Compare December 12, 2023 06:30
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3e329a6 to 24ff0ff Compare January 13, 2024 02:23
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 13, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 24ff0ff to 23a9d4c Compare February 6, 2024 19:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 23a9d4c to 423b1c4 Compare February 7, 2024 15:20
@tomosterlund tomosterlund merged commit 093a48f into master Feb 23, 2024
7 of 8 checks passed
@renovate renovate bot deleted the renovate/major-semantic-release-monorepo branch February 23, 2024 17:43
@felix-berlin
Copy link
Collaborator

🎉 This PR is included in version 3.9.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

3 participants