Drop Debian Bullseye #382
Merged
Drop Debian Bullseye #382
+8
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 tasks
frenck
approved these changes
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think now is the time to drop support for Debian Bullseye, I held off because of the privilege issues we were having in the past but I have not seen any issues pop up recently in regards to that and in my own testing it seems it has been solved by home-assistant/version#370, home-assistant/supervisor#4381 and home-assistant/version#372. Thus I am now comfortable with dropping Debian 11 Bullseye
Link to related Supervisor PR: home-assistant/supervisor#5335
Yes I did bump the version to 2.0.0 I figured it made sense given this is a breaking change