Skip to content

Lock file maintenance - #1183

Merged
renovate[bot] merged 5 commits into
mainfrom
renovate/lock-file-maintenance
Sep 21, 2026
Merged

renovate[bot] merged 5 commits into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 added the dependencies Pull requests that update dependencies label Sep 21, 2026
@renovate
renovate Bot enabled auto-merge (squash) September 21, 2026 00:39
renovate-approve[bot]
renovate-approve Bot previously approved these changes Sep 21, 2026
@renovate

renovate Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor Author

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.

@tnotheis
tnotheis force-pushed the renovate/lock-file-maintenance branch from ec015ac to 9ca6353 Compare September 21, 2026 07:53
@tnotheis

Copy link
Copy Markdown
Member

@Milena-Czierlinski I decided to pin the credo-ts libraries version to 0.7.0, because release 0.7.1 seems to be made accidentally and I don't think it's a good idea to use a version that wasn't released on purpose.
The reasons why I think the version was released accidentally are:

  1. it's only a patch version, but there is at least one breaking change (as you can see in the failing pipelines).
  2. the release notes only mention 1 change, while in reality there are 123 commits between Tag v0.7.0 and v0.7.1.

@renovate
renovate Bot merged commit 2a1e1d6 into main Sep 21, 2026
15 checks passed
@renovate
renovate Bot deleted the renovate/lock-file-maintenance branch September 21, 2026 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant