-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Bump Microsoft.AspNetCore.Server.IIS from 2.2.0 to 2.2.6 in /src/Servers/IIS/IIS/test/testassets/InProcessNewShimWebSite #42624
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
Conversation
Bumps [Microsoft.AspNetCore.Server.IIS](https://github.com/aspnet/AspNetCore) from 2.2.0 to 2.2.6. - [Release notes](https://github.com/aspnet/AspNetCore/releases) - [Changelog](https://github.com/dotnet/aspnetcore/blob/main/docs/ReleasePlanning.md) - [Commits](2.2.0...v2.2.6) --- updated-dependencies: - dependency-name: Microsoft.AspNetCore.Server.IIS dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
src/Servers/IIS/IIS/test/testassets/InProcessNewShimWebSite/InProcessNewShimWebSite.csproj
Show resolved
Hide resolved
Approved and enabled auto-squish |
Ugh, the InProcessNewShimWebSite project only references 2.2-era packages and no new product code (aside from the installed ANCM shim). Should I change the test to use the current shared framework instead❔ Or, should the test asset and tests that use it be removed❔ |
619a7d9
to
ab518bb
Compare
Simplest change was the original one. But we can still remove the test asset if anyone feels that's better. Reverted the PR title too. |
@Tratcher please approve if you agree on this approach |
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.
This is fine for now, but @HaoK, we should look at getting rid of such tests. They don't make sense anymore.
@Tratcher exactly what tests are no longer needed, the new shim/old shim tests? |
The tests that rely on the 2.2 packages, unless we can refactor them to target 3.1. |
Bumps Microsoft.AspNetCore.Server.IIS from 2.2.0 to 2.2.6.
Release notes
Sourced from Microsoft.AspNetCore.Server.IIS's releases.
Commits
e7f262e
Merge in 'release/2.2' changes2c9e5c9
Merge branch 'release/2.1' => 'release/2.2' #11236d2327a5
Merge branch 'release/2.1' into release/2.219dc9d1
Merge in 'release/2.2' changesd858156
Fix order in which EF properties are set21f6b5f
Update submodules.props for EF 2.2.6f74ca43
Always include ANCM in build output (#11199)2b771cd
Merge in 'release/2.2' changes0460bc3
Always include ANCM in build output (#11198)39c7419
Merge in 'release/2.2' changesDependabot 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 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.