Remove latest/(stable|beta|candidate) tracks for self-signed-certificates

We would like to delist/remove every self-signed-certificates charm Charmhub | Deploy Self Signed X.509 Certificates using Charmhub - The Open Operator Collection published under the latest/(stable|beta|candidate) tracks and only keep the latest/edge ones

Pausing the request for now while we check on the deprecation notice

@shipperizer for the history, Data team (at least) uses latest/stable in many internal CI tests and it is a default config for all our Terraform plans.

Simply deleting/closing the latest/stable will have a dramatic effect on us… maybe you can announce it properly and give us change to migrate to (1/stable?)

P.S. I have noticed this post by luck only… I see no deprecation announce of latest/stable tracks. Did I miss them?

I believe the team has stopped publishing to the latest tracks back in march, but i m gonna double check if we ever issued a formal deprecation notice

if not we will write up something and send a proper comm out

my bad for not checking this beforehand

@taurus we had something in here https://charmhub.io/self-signed-certificates/docs/tracks-and-compatibility#p-36847-juju-version-compatibility

we ll look at making it more evident via a discourse post

3 Likes