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.

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

chore(deps): update dependency semantic-release to v22 - autoclosed #148

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency semantic-release to v22 - autoclosed #148

wants to merge 1 commit into from

Conversation

open-turo-bot
Copy link
Contributor

@open-turo-bot open-turo-bot commented Sep 17, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
semantic-release devDependencies major 21.1.1 -> 22.0.12

Release Notes

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

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

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 Renovate Bot.

@open-turo-bot open-turo-bot requested a review from a team as a code owner September 17, 2023 00:20
@open-turo-bot
Copy link
Contributor Author

open-turo-bot commented Sep 17, 2023 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"22.0.12" from the root project
npm ERR!   peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/commit-analyzer
npm ERR!     @semantic-release/commit-analyzer@"^10.0.4" from the root project
npm ERR!   5 more (@semantic-release/exec, @semantic-release/git, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@"^21.0.2" from [email protected]
npm ERR! node_modules/gradle-semantic-release-plugin
npm ERR!   gradle-semantic-release-plugin@"^1.7.7" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@"^21.0.2" from [email protected]
npm ERR!   node_modules/gradle-semantic-release-plugin
npm ERR!     gradle-semantic-release-plugin@"^1.7.7" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-13T00_20_35_007Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-13T00_20_35_007Z-debug-0.log

@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch 3 times, most recently from b7d141d to 5a7bbcc Compare September 25, 2023 00:20
@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch 2 times, most recently from 48f690e to 2e95e25 Compare October 25, 2023 00:19
@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch 2 times, most recently from 137282a to 0afc119 Compare November 4, 2023 00:19
@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch from 0afc119 to 5b4e2f8 Compare November 18, 2023 00:20
@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch 3 times, most recently from f986eb3 to 3b0ace4 Compare December 12, 2023 00:21
@open-turo-bot open-turo-bot force-pushed the c/renovate_major-22-semantic-release-monorepo branch from 3b0ace4 to 2ad0037 Compare December 13, 2023 00:20
@github-actions GitHub Actions
Copy link

Release notes preview

No new release will be created.

If you are expecting a release, you will need to either fix a bug or add a feature.
Chores, CI, docs, refactoring, style and other changes will not trigger a release.

@open-turo-bot open-turo-bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v22 - autoclosed Jan 3, 2024
@open-turo-bot open-turo-bot deleted the c/renovate_major-22-semantic-release-monorepo branch January 3, 2024 13:24
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.
2 participants
@open-turo-bot @renovate-bot