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): bump bytestream/horde-imap-client from 2.33.2 to ^2.33.3 (main) #10335

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
bytestream/horde-imap-client (source) ^2.33.2 -> ^2.33.3 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

bytestream/Imap_Client (bytestream/horde-imap-client)

v2.33.3

Compare Source

What's Changed

New Contributors

Full Changelog: bytestream/Imap_Client@v2.33.2...v2.33.3


Configuration

📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, 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

This PR was generated by Mend Renovate. View the repository job log.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot merged commit 9c43e51 into main Nov 11, 2024
35 checks passed
@renovate renovate bot deleted the renovate/main-bytestream-horde-imap-client-2.x branch November 11, 2024 14:25
@st3iny
Copy link
Member

st3iny commented Nov 12, 2024

/backport to stable4.0

@st3iny
Copy link
Member

st3iny commented Nov 12, 2024

/backport to stable3.7

Copy link

backportbot bot commented Nov 12, 2024

The backport to stable4.0 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable4.0
git pull origin stable4.0

# Create the new backport branch
git checkout -b backport/10335/stable4.0

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 8c838b42

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/10335/stable4.0

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Copy link

backportbot bot commented Nov 12, 2024

The backport to stable3.7 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable3.7
git pull origin stable3.7

# Create the new backport branch
git checkout -b backport/10335/stable3.7

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 8c838b42

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/10335/stable3.7

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant