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.

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

Update Pulumi codegen to net6.0 #11543

Merged
merged 4 commits into from Jan 4, 2023
Merged

Update Pulumi codegen to net6.0 #11543

merged 4 commits into from Jan 4, 2023

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented Dec 6, 2022

Description

.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates sdkgen to only 6.0 as well.

We'll need to ensure the version number in pkg/codegen/dotnet/gen.go matches the version number that pulumi/pulumi-dotnet#10 release as.

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have run make changelog and committed the changelog/pending/<file> documenting my change
  • Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

@pulumi-bot
Copy link
Contributor

pulumi-bot commented Dec 6, 2022

Changelog

[uncommitted] (2023-01-04)

Features

  • [sdk/dotnet] Drop support for .NET Core 3.1.
    #11543

@Frassle
Copy link
Member Author

Frassle commented Dec 6, 2022

Do not merge, we'll move this to the new dotnet sdk and merge it that side.

@mikhailshilkov
Copy link
Member

What are the benefits of doing it and downsides of keeping 3.1? Just curious.

@Frassle
Copy link
Member Author

Frassle commented Dec 7, 2022

What are the benefits of doing it and downsides of keeping 3.1?

Benefit is if anyone is still targeting 3.1 they could keep building against Pulumi.

Downside is it limits the api area of dotnet we can use (there's quite a few useful things added in 6.0).
We're also not testing or supporting 3.1 (and neither is Microsoft).

@mikhailshilkov
Copy link
Member

there's quite a few useful things added in 6.0

That's interesting. Any concrete enhancements that you have in mind that we can apply now?

@Frassle
Copy link
Member Author

Frassle commented Dec 8, 2022

Any concrete enhancements that you have in mind that we can apply now?

Not of the top of my head. I know it's been something I've hit a few times in the past doing dotnet changes, generally just small stuff that could be worked around.
Most recent was there's quite a few new options in System.Text.Json in 6.0 compared to 3.1 that I saw while looking into #11556.

Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 15, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been
targetting only 6.0 for a while now as well.

This updates sdkgen to only 6.0 as well.
@Frassle Frassle changed the title Update Pulumi projects to net6.0 Update Pulumi codegen to net6.0 Dec 15, 2022
Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 19, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 19, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 22, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 22, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
Frassle added a commit to pulumi/pulumi-dotnet that referenced this pull request Dec 28, 2022
.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates the core porjects to only 6.0 as well.

We'll still want to do pulumi/pulumi#11543 in
pu/pu to update sdkgen.
pkg/codegen/dotnet/gen.go Outdated Show resolved Hide resolved
Copy link
Contributor

@kpitzen kpitzen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending my one question.

net6 can reference net3.1
@Frassle
Copy link
Member Author

Frassle commented Jan 4, 2023

bors merge

bors bot added a commit that referenced this pull request Jan 4, 2023
11543: Update Pulumi codegen to net6.0 r=Frassle a=Frassle

<!--- 
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates sdkgen to only 6.0 as well.

We'll need to ensure the version number in pkg/codegen/dotnet/gen.go matches the version number that pulumi/pulumi-dotnet#10 release as.

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->


11766: Changelog and go.mod updates for v3.51.0 r=pulumi-bot a=pulumi-bot

bors merge

Co-authored-by: Fraser Waters <fraser@pulumi.com>
Co-authored-by: github-actions <github-actions@github.com>
@bors
Copy link
Contributor

bors bot commented Jan 4, 2023

Canceled.

@Frassle
Copy link
Member Author

Frassle commented Jan 4, 2023

bors merge

bors bot added a commit that referenced this pull request Jan 4, 2023
11543: Update Pulumi codegen to net6.0 r=Frassle a=Frassle

<!--- 
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

.NET Core 3.1 is out of support on December 13th:
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

We've already stopped testing on .NET Core 3.1, and program gen has been targeting only 6.0 for a while now as well.

This updates sdkgen to only 6.0 as well.

We'll need to ensure the version number in pkg/codegen/dotnet/gen.go matches the version number that pulumi/pulumi-dotnet#10 release as.

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my feature works
<!--- 
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->


11766: Changelog and go.mod updates for v3.51.0 r=pulumi-bot a=pulumi-bot

bors merge

Co-authored-by: Fraser Waters <fraser@pulumi.com>
Co-authored-by: github-actions <github-actions@github.com>
@bors
Copy link
Contributor

bors bot commented Jan 4, 2023

Canceled.

@Frassle
Copy link
Member Author

Frassle commented Jan 4, 2023

bors merge

@bors
Copy link
Contributor

bors bot commented Jan 4, 2023

Build succeeded:

  • bors-ok

@bors bors bot merged commit e6167e9 into master Jan 4, 2023
@bors bors bot deleted the fraser/rmdotnetcore31 branch January 4, 2023 19:22
bors bot added a commit that referenced this pull request Jan 10, 2023
11818: Revert "Update Pulumi codegen to net6.0" r=t0yv0 a=t0yv0

Reverts #11543

After discussing with `@danielrbradley` the providers ecosystem is not ready for releasing this yet, as auto-merge workflows will blow up providers CI. Tracking merging pre-requisites first in https://github.com/pulumi/home/issues/2531 which will unblock this.

Co-authored-by: Anton Tayanovskyy <anton.tayanovskyy@gmail.com>
bors bot added a commit that referenced this pull request Jan 10, 2023
11818: Revert "Update Pulumi codegen to net6.0" r=t0yv0 a=t0yv0

Reverts #11543

After discussing with `@danielrbradley` the providers ecosystem is not ready for releasing this yet, as auto-merge workflows will blow up providers CI. Tracking merging pre-requisites first in https://github.com/pulumi/home/issues/2531 which will unblock this.

Co-authored-by: Anton Tayanovskyy <anton.tayanovskyy@gmail.com>
bors bot added a commit that referenced this pull request Jan 11, 2023
11818: Revert "Update Pulumi codegen to net6.0" r=t0yv0 a=t0yv0

Reverts #11543

After discussing with `@danielrbradley` the providers ecosystem is not ready for releasing this yet, as auto-merge workflows will blow up providers CI. Tracking merging pre-requisites first in https://github.com/pulumi/home/issues/2531 which will unblock this.

Co-authored-by: Anton Tayanovskyy <anton.tayanovskyy@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants