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

Feature: Update Project to .NET 8 or 9 Due to .NET 6.0 End of Life #215

Open
ricoroodenburg opened this issue Jan 4, 2025 · 9 comments
Open
Labels
enhancement New feature or request
Milestone

Comments

@ricoroodenburg
Copy link

The project currently targets .NET 6.0, which is now end-of-life as per the official Microsoft support policy: Microsoft .NET Support Policy. To ensure long-term support, security, and compatibility, the project should be updated to .NET 8 or 9.

@ricoroodenburg ricoroodenburg added the enhancement New feature or request label Jan 4, 2025
@amadeo-alex
Copy link
Collaborator

Fair point, I'll make it a 2.2 deliverable.

@amadeo-alex amadeo-alex added this to the 2.2.0 milestone Jan 6, 2025
@ricoroodenburg
Copy link
Author

If I can help you with testing, please let me know!

@ricoroodenburg
Copy link
Author

ricoroodenburg commented Jan 8, 2025

Do you happen to know when it will be released? I understand that it's open source, so there might not be a fixed deadline. I'm really grateful for your help!

@DyadicOne
Copy link

Hi! Literally just made a GitHub account because of this awesome integration (thanks for your work in advancing it!). I'm eager to install, but waiting for the .NET 8/9 update before doing so. Do you have a vague guestimate re. when this might be released?

Thanks.

@amadeo-alex
Copy link
Collaborator

I still have additional checks to do but looks it was as simple as just changing the target framework version - if so it'll be part of 2.2.0-beta1.

@ricoroodenburg
Copy link
Author

I still have additional checks to do but looks it was as simple as just changing the target framework version - if so it'll be part of 2.2.0-beta1.

Sounds good!

@DyadicOne
Copy link

DyadicOne commented Jan 29, 2025

I still have additional checks to do but looks it was as simple as just changing the target framework version - if so it'll be part of 2.2.0-beta1.

Legend!! Thanks for jumping on this - appreciated :)

Please forgive a silly question: I've never used GitHub before, what is a beta-1 release? Does it replace the current main download, or will I need to go somewhere else to get it? Is there a way for me to be alerted when it is available? Again, apologies for newcomer basic questions!

@amadeo-alex
Copy link
Collaborator

That usually depends mostly on a project-project basis but for HASS.Agent "betaX" releases are the ones that are not available by default.
They do show in https://github.com/hass-agent/HASS.Agent/releases but have the "Pre-release" badge. Same applies for the app itself, it'll only show "beta update available notification" if that option is selected in the configuration.

The beta releases are basically versions with new features/bug fixes that might be a bit unstable due to the recent changes. Usually nothing gamebreaking but a new "bug" might sneak in while fixing the original one for example. Doing betas allows ppl impacted with a bug to have the fix early.

The numbers after "beta" are just iterations of beta versions - for example for 2.1.1 version (which a bugfix release for 2.1.0) we are currently at beta3.

@DyadicOne
Copy link

Awesome, thanks for taking the time to explain - greatly appreciated!

I'm looking forward to 2.2.0-beta1 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants