Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 25, 2025

Bumps vite from 5.4.14 to 5.4.15.

Release notes

Sourced from vite's releases.

v5.4.15

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.15 (2025-03-24)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @nextcloud-command.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.14 to 5.4.15.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.15/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.15/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Javascript related ticket labels Mar 25, 2025
Copy link
Contributor

@nextcloud-command nextcloud-command left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dependabot merge

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 25, 2025

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@skjnldsv skjnldsv merged commit 8c9bf9c into master Mar 25, 2025
28 of 31 checks passed
@skjnldsv skjnldsv deleted the dependabot/npm_and_yarn/vite-5.4.15 branch March 25, 2025 19:24
@skjnldsv
Copy link
Member

/backport c2898fe to stable31

@backportbot backportbot bot added the backport-request Pending backport by the backport-bot label Mar 26, 2025
@skjnldsv
Copy link
Member

/backport c2898fe to stable30

@backportbot backportbot bot removed the backport-request Pending backport by the backport-bot label Mar 26, 2025
@skjnldsv
Copy link
Member

Ahahah you can even backport random commits 😁

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot backportbot bot added the backport-request Pending backport by the backport-bot label Mar 26, 2025
@backportbot backportbot bot removed the backport-request Pending backport by the backport-bot label Mar 26, 2025
@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot backportbot bot added the backport-request Pending backport by the backport-bot label Mar 26, 2025
@backportbot
Copy link

backportbot bot commented Mar 26, 2025

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/2765/stable29

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/2765/stable29

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/2765/stable29')
fatal: a branch named 'backport/2765/stable29' already exists


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

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot
Copy link

backportbot bot commented Mar 26, 2025

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/2765/stable29

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/2765/stable29

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/2765/stable29')
fatal: a branch named 'backport/2765/stable29' already exists


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

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot
Copy link

backportbot bot commented Mar 26, 2025

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/2765/stable29

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/2765/stable29

Error: Failed to clone repository: Failed to create working tree: error: pathspec 'master
' did not match any file(s) known to git


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

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot
Copy link

backportbot bot commented Mar 26, 2025

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/2765/stable29

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/2765/stable29

Error: Failed to clone repository: Failed to create working tree: error: pathspec 'master
' did not match any file(s) known to git


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

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot
Copy link

backportbot bot commented Mar 26, 2025

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/2765/stable29

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

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/2765/stable29

Error: Failed to clone repository: Failed to create working tree: Preparing worktree (new branch 'backport/2765/stable29')
fatal: a branch named 'backport/2765/stable29' already exists


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

@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot backportbot bot removed the backport-request Pending backport by the backport-bot label Mar 26, 2025
@skjnldsv
Copy link
Member

/backport c2898fe to stable29

@backportbot backportbot bot added the backport-request Pending backport by the backport-bot label Mar 26, 2025
@backportbot backportbot bot removed the backport-request Pending backport by the backport-bot label Mar 26, 2025
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 javascript Javascript related ticket

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants