mastodon
Upgrade to Mastodon v4.1.9
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.8 v4.1.9
mastodon
mastodon
Upgrade to Mastodon v4.1.7
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.7
mastodon
Upgrade to Mastodon v4.1.6
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.6
mastodon
Upgrade to Mastodon v4.1.5
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.5
mastodon
Upgrade to Mastodon v4.1.4
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.3 v4.1.4
mastodon
Upgrade to Mastodon v4.1.2
Minor update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.2
mastodon
Upgrade to Mastodon v4.1.1
Minor update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.1 The database health check in the Docker compose file has to be updated to look like, which are indeed the default values: healthcheck: test: ['CMD', '
mastodon
Upgrade to Mastodon v4.1.0
Minor update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.1.0
mastodon
Upgrade to Mastodon v4.0.2
Major update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.0.0 v4.0.1 v4.0.2
mastodon
Upgrade to Mastodon v3.5.5
Micro update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v3.5.2 v3.5.3 v3.5.4 v3.5.5