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 dependency semantic-release to v22 #24649

Merged
merged 1 commit into from Sep 26, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 25, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 21.1.2 -> 22.0.0 age adoption passing confidence

Release Notes

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

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.

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.

πŸ”• 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.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d22e921 to ea236a6 Compare September 25, 2023 14:43
@rarkins
Copy link
Collaborator

rarkins commented Sep 25, 2023

@travi csn you help us understand if the conventional-changelog-presets change is applicable to us? I don't understand it

@travi
Copy link
Contributor

travi commented Sep 25, 2023

since you are not using the default preset, this does impact you. you can find a bit more detail in semantic-release/semantic-release#2929. in short, the api of the official conventional-changelog presets were made consistent across the presets as breaking changes. when using the latest version of the preset with the previous major of semantic-release, loading the preset would fail. even worse it would fail silently in some cases (depending on preset).

since it looks like your preset has already been updated to the latest major, you likely are already in the situation that causes semantic-release to fail, so i recommend applying this update to get back to a fully working release configuration.

@travi
Copy link
Contributor

travi commented Sep 25, 2023

one final note, if you happen to be using any of our private APIs, v22 defines exports which limited access to those internals. https://github.com/semantic-release/semantic-release/releases/tag/v22.0.3 reverted that change for the time being, but mentioning in case that applies to you so that you can update past that revert. if it does happen you apply to your usage, it would also be helpful if you could follow along with semantic-release/semantic-release#2978

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ea236a6 to 88fc412 Compare September 26, 2023 04:48
| datasource | package          | from   | to     |
| ---------- | ---------------- | ------ | ------ |
| npm        | semantic-release | 21.1.2 | 22.0.0 |
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 88fc412 to e7deb82 Compare September 26, 2023 07:47
@viceice
Copy link
Member

viceice commented Sep 26, 2023

it seems that preset works with v21 and v22, so this update should be safe.

@rarkins rarkins added this pull request to the merge queue Sep 26, 2023
Merged via the queue into main with commit c3baf42 Sep 26, 2023
37 checks passed
@rarkins rarkins deleted the renovate/major-semantic-release-monorepo branch September 26, 2023 12:03
@renovate-release
Copy link
Collaborator

πŸŽ‰ This PR is included in version 36.107.3 πŸŽ‰

The release is available on:

Your semantic-release bot πŸ“¦πŸš€

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants