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

fix(deps): update dependency @nextcloud/l10n to v2 (main) #3685

Merged
merged 2 commits into from
Feb 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nextcloud/l10n ^1.6.0 -> ^2.0.1 age adoption passing confidence

Release Notes

nextcloud/nextcloud-l10n

v2.0.1

Compare Source

Full Changelog

Fixed
Changed
  • Dependency updates

v2.0.0

Compare Source

Full Changelog

Changed

From 2.0.0, this package is standalone and do not rely on window OC variables to function.

Fixed

Configuration

📅 Schedule: Branch creation - "before 5am every weekday,every weekend" in timezone Europe/Berlin, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 20, 2023
@renovate renovate bot requested review from a team, marcelklehr and luka-nextcloud and removed request for a team January 20, 2023 00:30
@mejo- mejo- force-pushed the renovate/main-nextcloud-l10n-2.x branch from c60ea51 to 51ab5cf Compare January 20, 2023 00:56
@renovate renovate bot force-pushed the renovate/main-nextcloud-l10n-2.x branch 2 times, most recently from 250ed29 to 2ab1ee5 Compare January 25, 2023 10:47
@juliusknorr
Copy link
Member

/compile amend /

@renovate renovate bot force-pushed the renovate/main-nextcloud-l10n-2.x branch from 2ab1ee5 to 52796a5 Compare January 27, 2023 17:36
@mejo- mejo- force-pushed the renovate/main-nextcloud-l10n-2.x branch from 52796a5 to 6d8cb19 Compare January 28, 2023 14:37
@renovate renovate bot force-pushed the renovate/main-nextcloud-l10n-2.x branch 2 times, most recently from 4f5a1ce to c17d9c1 Compare February 1, 2023 15:20
@juliusknorr
Copy link
Member

@mejo- mejo- force-pushed the renovate/main-nextcloud-l10n-2.x branch from c17d9c1 to c0c2881 Compare February 14, 2023 09:18
@renovate renovate bot force-pushed the renovate/main-nextcloud-l10n-2.x branch from c0c2881 to 6a57938 Compare February 18, 2023 09:13
@max-nextcloud
Copy link
Collaborator

/compile

Signed-off-by: nextcloud-command <[email protected]>
@renovate
Copy link
Contributor Author

renovate bot commented Feb 18, 2023

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.

@cypress
Copy link

cypress bot commented Feb 18, 2023

Passing run #8642 ↗︎

0 135 0 0 Flakiness 0

Details:

fix(deps): update dependency @nextcloud/l10n to v2 (main)
Project: Text Commit: e759ef6452
Status: Passed Duration: 03:27 💡
Started: Feb 18, 2023 10:05 AM Ended: Feb 18, 2023 10:08 AM

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.

@max-nextcloud max-nextcloud merged commit e7ffa52 into main Feb 18, 2023
@delete-merged-branch delete-merged-branch bot deleted the renovate/main-nextcloud-l10n-2.x branch February 18, 2023 10:19
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants