Upgrade from `net471` to LTS (or current) image tag
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
Research direction
Open non-lts/Dockerfile at the six referenced lines (4, 10, 15, 23, 26, and 21) and inspect each image tag targeting net471. Update those images to net48 or the current release, then confirm all six entries no longer use the unsupported target; if any must remain, review the documented dotnet-versionsweeper.json ignore configuration instead.
Written by the indexing model from the issue text.
Description
The following Dockerfile(s) target a .NET version which is no longer supported.
This is an auto-generated issue, detailed and discussed in dotnet/docs#22271.
| Target version | End of life | Release notes | Nearest LTS TFM version |
|---|---|---|---|
net471 |
N/A | net471 release notes | net48 |
- non-lts/Dockerfile
- non-lts/Dockerfile
- non-lts/Dockerfile
- non-lts/Dockerfile
- non-lts/Dockerfile
- non-lts/Dockerfile
Consider upgrading Dockerfile images to either the current release, or the nearest LTS TFM version.
If any of these Dockerfile(s) listed in this issue are intentionally targeting an unsupported version,
you can optionally configure to ignore these results in future automation executions.
Create a (or update the) dotnet-versionsweeper.json file at the root of the repository and
add an ignore entry following the
globbing patterns detailed here.
{
"ignore": [
"**/path/to/Dockerfile"
]
}
- Dominant language
- C#
- Stars
- 65
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/versionsweeper
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/versionsweeper#145 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dotnet/versionsweeper#108 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
dotnet/versionsweeper#103 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dotnet/versionsweeper#101 ·
-
dotnet-target-version
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dotnet/versionsweeper#100 ·
All issues in dotnet/versionsweeper
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·