Auto-removal on archived packages

System Health details

Not applicable

Checklist

• I’m running the newest version of HACS https://github.com/hacs/integration/releases/latest
• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• I have read https://hacs.xyz/docs/issues
• This issue is related to the backend (integration part) of HACS.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of currently open or issues pending release.

Describe the issue

I’m referring to this PR: https://github.com/hacs/default/pull/1373

There was no warning, no deprecation notice, no nothing. HACS just automatically removed packages in which my setup relies heavily on. This is not good user experience and I’m a bit set back by just how bad this was handled.

Might I suggest you properly indicate when packages have been archived to allow people chance to prepare for breaking changes instead of having them automatically removed from our configurations? Or give people the ability to keep what is already installed, installed with proper warnings or indications that there will no longer be updates?

This whole process really needs some well documented steps and expectations moving forward.

Reproduction steps

Not applicable

Debug logs

Not applicable

Diagnostics dump

No response

[shbatm]

Confirming @ludeeus’s test. Was removed from the store but not uninstalled on my instance.

[mririgoyen]

This was so absolutely mishandled. Autoremoval of code/features with no warnings, no deprecations, no nothing is not something I will tolerate.

HACS needs to put proper process around this. They are NOT the gatekeepers of my instance and should not be able to automatically remove things without MY intervention. If they do not address this immediately, I will be removing it and going back to manually adding custom components and integrations.

This is completely unacceptable.