chore(deps): bump @scalar/api-reference from 1.43.15 to 1.43.17#10064
Conversation
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 3 minutes 14 seconds in the queue, with no time running CI. ReasonThe pull request conflicts with pull requests ahead in queue: #10053, #10054, #10055, #10056, #10057, #10058, #10060, #10062 HintThere is nothing you can do for now. If the pull request ahead in the queue is merged, this pull request will become conflicting and you'll have to update it. |
|
@dependabot[bot] this pull request is now in conflict 😩 |
Bumps [@scalar/api-reference](https://github.com/scalar/scalar/tree/HEAD/packages/api-reference) from 1.43.15 to 1.43.17. - [Release notes](https://github.com/scalar/scalar/releases) - [Changelog](https://github.com/scalar/scalar/blob/main/packages/api-reference/CHANGELOG.md) - [Commits](https://github.com/scalar/scalar/commits/HEAD/packages/api-reference) --- updated-dependencies: - dependency-name: "@scalar/api-reference" dependency-version: 1.43.17 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
0a59f2d to
c0ddef4
Compare
Merge Queue Status✅ The pull request has been merged at c0ddef4 This pull request spent 7 minutes 27 seconds in the queue, including 1 minute 37 seconds running CI. Required conditions to merge
|
Bumps @scalar/api-reference from 1.43.15 to 1.43.17.
Changelog
Sourced from
@scalar/api-reference's changelog.Commits
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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)