-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore(deps): Bump @nextcloud/initial-state from 2.1.0 to 2.2.0 #283
chore(deps): Bump @nextcloud/initial-state from 2.1.0 to 2.2.0 #283
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dependabot merge
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. |
Bumps [@nextcloud/initial-state](https://github.com/nextcloud/nextcloud-initial-state) from 2.1.0 to 2.2.0. - [Release notes](https://github.com/nextcloud/nextcloud-initial-state/releases) - [Changelog](https://github.com/nextcloud-libraries/nextcloud-initial-state/blob/main/CHANGELOG.md) - [Commits](nextcloud-libraries/nextcloud-initial-state@v2.1.0...v2.2.0) --- updated-dependencies: - dependency-name: "@nextcloud/initial-state" dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
a24b185
to
b5bda22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dependabot merge
/compile / |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
Bumps @nextcloud/initial-state from 2.1.0 to 2.2.0.
Release notes
Sourced from
@nextcloud/initial-state
's releases.Changelog
Sourced from
@nextcloud/initial-state
's changelog.Commits
95efdb8
Merge pull request #682 from nextcloud-libraries/chore/2-2-0fff5dae
chore: Prepare v2.2.0 release1933658
Merge pull request #681 from nextcloud-libraries/dependabot/npm_and_yarn/vite...4e585a3
chore(deps-dev): Bump@vitest/coverage-v8
from 1.5.0 to 1.5.2b292d1f
Merge pull request #680 from nextcloud-libraries/dependabot/npm_and_yarn/next...049dd90
chore(deps-dev): Bump@nextcloud/vite-config
from 1.2.2 to 1.2.364c0f71
fix: Adjust README26984f8
Merge pull request #679 from nextcloud-libraries/update-workflows3f8d8d1
fix(CI): Update workflows from from organization8504f30
Merge pull request #678 from nextcloud-libraries/feat/migrate-viteDependabot 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)