Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 13.0.0 -> 13.0.1 age adoption passing confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.1

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

@renovate renovate bot added the 📦️ Dependencies Pull requests that update a dependency file label Jan 4, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Jan 4, 2025

⚠️ 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: pnpm-lock.yaml
Scope: all 13 workspace projects
.                                        |  WARN  Ignoring broken lockfile at /tmp/renovate/repos/github/JeromeFitz/packages: The lockfile at "/tmp/renovate/repos/github/JeromeFitz/packages/pnpm-lock.yaml" is broken: duplicated mapping key (6682:3)

 6679 |     transitivePeerDependencies:
 6680 |       - supports-color
 6681 | 
 6682 |   [email protected]:
----------^
 6683 |     dependencies:
 6684 |       debug: 4.4.0
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 61, reused 0, downloaded 0, added 0
Progress: resolved 145, reused 0, downloaded 0, added 0
Progress: resolved 224, reused 0, downloaded 0, added 0
Progress: resolved 327, reused 0, downloaded 0, added 0
Progress: resolved 543, reused 0, downloaded 0, added 0
Progress: resolved 676, reused 0, downloaded 0, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: @semantic-release/[email protected]

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@renovate renovate bot force-pushed the deps/semantic-release-commit-analyzer-13.x branch from 726b740 to b0e4937 Compare January 9, 2025 21:16
@JeromeFitz JeromeFitz force-pushed the deps/semantic-release-commit-analyzer-13.x branch from b0e4937 to e4b091c Compare January 9, 2025 21:18
@renovate
Copy link
Contributor Author

renovate bot commented Jan 9, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@JeromeFitz JeromeFitz added the 🥳️ LGTM Automerge: Let's Get This Merged label Jan 9, 2025
@kodiakhq kodiakhq bot merged commit 1ccc401 into main Jan 9, 2025
2 checks passed
@kodiakhq kodiakhq bot deleted the deps/semantic-release-commit-analyzer-13.x branch January 9, 2025 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📦️ Dependencies Pull requests that update a dependency file 🥳️ LGTM Automerge: Let's Get This Merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant