Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade from net7.0 to LTS (or STS) version #40684

Closed
github-actions bot opened this issue May 1, 2024 · 2 comments · Fixed by #41013
Closed

Upgrade from net7.0 to LTS (or STS) version #40684

github-actions bot opened this issue May 1, 2024 · 2 comments · Fixed by #41013
Labels
dotnet-target-version Issues and PRs automatically generated from the .NET version sweeper. Pri3 ⌚ Not Triaged Not triaged

Comments

@github-actions
Copy link
Contributor

github-actions bot commented May 1, 2024

The following project file(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
net7.0 May, 24 2024 net7.0 release notes net8.0

Consider upgrading projects to either the Standard Term Support (STS) or Long Term Support (LTS) versions.

If any of these projects 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/example.csproj"
    ]
}
@github-actions github-actions bot added the dotnet-target-version Issues and PRs automatically generated from the .NET version sweeper. label May 1, 2024
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label May 1, 2024
@rextor92
Copy link
Contributor

rextor92 commented May 9, 2024

I can update the samples if this is going to be manual

@IEvangelist
Copy link
Member

I'm fine with that, as long as you tag this issue in the PR. And let's add ignore rules for the projects that are intentionally targeting .NET 7, for example, that are within a 7.0 folder. (such as some of the Docker content).

rextor92 added a commit to rextor92/docs that referenced this issue May 20, 2024
@rextor92
Relates to dotnet#40684 | Updating to .NET 8 (pt1)
0ce26dd
rextor92 added a commit to rextor92/docs that referenced this issue May 20, 2024
@rextor92
dotnet#40684 : Updating to .NET 8 (pt2)
10420b1
@rextor92 rextor92 mentioned this issue May 20, 2024
Merged
2 tasks
IEvangelist pushed a commit that referenced this issue May 29, 2024
@rextor92
Update snippets to dotnet8 (#41013)
fd5dfd0 
* Relates to #40684 | Updating to .NET 8 (pt1)

* #40684 : Updating to .NET 8 (pt2)

* Added binaryformatter to versionsweeper and keeping it on .NET 6 as its deprecated later

* Addressing #41013 comments

* Moved c# and vb samples to only have 1 sln in a root folder

* reverting last commit

* updating githubaction csproj

* deleting solution files

* inlined type forwarding examples
@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged and removed ⌚ Not Triaged Not triaged labels May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dotnet-target-version Issues and PRs automatically generated from the .NET version sweeper. Pri3 ⌚ Not Triaged Not triaged
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update snippets to dotnet8 rextor92/docs
3 participants
@IEvangelist @dotnet-bot @rextor92