-
Notifications
You must be signed in to change notification settings - Fork 756
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
failing tests: Bump @vscode-elements/react-elements from 0.5.0 to 0.7.0 in /src/vscode-bicep #15551
Conversation
dependabot
bot
commented
on behalf of github
Nov 10, 2024
•
edited by microsoft-github-policy-service
bot
Loading
edited by microsoft-github-policy-service
bot
Bumps @vscode-elements/react-elements from 0.5.0 to 0.7.0. --- updated-dependencies: - dependency-name: "@vscode-elements/react-elements" dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
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.
Test this change out locally with the following install scripts (Action run 11788633246) VSCode
Azure CLI
|
Dotnet Test Results 72 files - 36 72 suites - 36 27m 43s ⏱️ - 14m 10s Results for commit e3c611d. ± Comparison against base commit 430b484. This pull request removes 1850 and adds 630 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Pull request was closed
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Forcing rebuild |
@shenglol Is it logical/okay to assign this to you (no rush)? I've retried a couple of times, but the failures are consistent in vscode extension tests. Thx.
|
Bumps @vscode-elements/react-elements from 0.5.0 to 0.7.0.
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 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)