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

feat: Migrate to .Net Core 3.1 #328

Conversation

Christian-Oleson
Copy link
Contributor

closes #277

Copy link
Collaborator

@ChrisKujawa ChrisKujawa left a comment

Choose a reason for hiding this comment

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

Thanks @Christian-Oleson

could you please adjust your commit messages and follow the contribution guide https://github.com/camunda-cloud/zeebe/blob/develop/CONTRIBUTING.md#commit-message-guidelines

@@ -13,7 +13,7 @@
<ItemGroup>
<PackageReference Include="Microsoft.Extensions.Configuration.FileExtensions" Version="3.1.19" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="5.0.2" />
<PackageReference Include="Microsoft.Extensions.Logging" Version="5.0.0" />
<PackageReference Include="Microsoft.Extensions.Logging" Version="3.1.19" />
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hm why this was dropped to a lower version ? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There were two completely different versions of Microsoft.Extensions.Logging here. I also found a lower version in Client.IntegrationTests.csproj. We should avoid multiple versions, so this consolidates Client.IntegrationTests.csproj from 3.1.14 to 3.1.19 while consolidating the 5.x version to 3.1.19. I would suggest moving both projects to 5.x when you move to 5.x (or really .NET 6)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @Christian-Oleson

could you please adjust your commit messages and follow the contribution guide https://github.com/camunda-cloud/zeebe/blob/develop/CONTRIBUTING.md#commit-message-guidelines

I think I fixed the commit message? Let me know if I'm misunderstanding anything.

feat: Migrate to .Net Core 3.1 from .NET Core 2.1
@Christian-Oleson Christian-Oleson force-pushed the feature/#277_Migrate_To_Net_Core_3_1 branch from a37c632 to 660c328 Compare October 4, 2021 13:17
@ChrisKujawa
Copy link
Collaborator

Thanks @Christian-Oleson still the title of the commit (or subject however you want to call it) is wrong, but should be fine for now. just for the next time :)

feat: Migrate to .Net Core 3.1 is the subject

@ChrisKujawa ChrisKujawa merged commit 972ca7f into camunda-community-hub:master Oct 5, 2021
@Christian-Oleson Christian-Oleson changed the title #277 - Migrate to .Net Core 3.1 feat: Migrate to .Net Core 3.1 Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate to .net core 3.1
2 participants