You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
__⚠️ Attention ⚠️__: the container name `voxpupuli/container-puppetserver` will be deprecated in 2025-02 and might be removed in the future. Please use `voxpupuli/puppetserver` instead.
I now wanted to switch to ghcr.io/voxpupuli/puppetserver:8.6.1-v1.6.0, ghcr.io/voxpupuli/puppetserver:8.7.0-v1.6.0 or some hypothetical ghcr.io/voxpupuli/puppetserver:8.7.0-v1.7.0.
Unfortunately, these container tags aren't available. It looks like only ghcr.io/voxpupuli/puppetserver:8.6.1-latest, ghcr.io/voxpupuli/puppetserver:8.6.1-main, ghcr.io/voxpupuli/puppetserver:8.7.0-latest or ghcr.io/voxpupuli/puppetserver:8.7.0-main are available.
What are your plans in that direction?
Are you planning to drop the "release" component? Will it stay with -latest/-main forever? Maybe just the git tag is missing?
What is your timeline on dropping the deprecated long container names (because we're now close to the announced 2025-02)?
The text was updated successfully, but these errors were encountered:
In the past, we used
ghcr.io/voxpupuli/container-puppetserver:8.6.1-v1.6.0
.Due to
container-puppetserver/README.md
Line 22 in ee3498f
I now wanted to switch to
ghcr.io/voxpupuli/puppetserver:8.6.1-v1.6.0
,ghcr.io/voxpupuli/puppetserver:8.7.0-v1.6.0
or some hypotheticalghcr.io/voxpupuli/puppetserver:8.7.0-v1.7.0
.Unfortunately, these container tags aren't available. It looks like only
ghcr.io/voxpupuli/puppetserver:8.6.1-latest
,ghcr.io/voxpupuli/puppetserver:8.6.1-main
,ghcr.io/voxpupuli/puppetserver:8.7.0-latest
orghcr.io/voxpupuli/puppetserver:8.7.0-main
are available.What are your plans in that direction?
Are you planning to drop the "release" component? Will it stay with
-latest
/-main
forever? Maybe just the git tag is missing?What is your timeline on dropping the deprecated long container names (because we're now close to the announced 2025-02)?
The text was updated successfully, but these errors were encountered: