Skip to content

Conversation

amercader
Copy link
Member

This allows users that really want to pin a specific release of the Docker images to stick with a particular one.
eg for the 2.11 images, in addition to:

ckan/ckan-base:2.11
ckan/ckan-base:2.11.0
ckan/ckan-base:2.11-py3.10
ckan/ckan-base:2.11.0-py3.10

We will publish this one:

ckan/ckan-base:2.11-py3.10-v20241111

(We don't need a ckan/ckan-base:2.11.0-py3.10-v20241111 one because bumping the patch release will mean doing a new Docker release)

This allows users that really want to pin a specific release of the
Docker images to stick with a particular one
Copy link
Contributor

@kowh-ai kowh-ai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there is definitely value in pinning a particular release!

@kowh-ai kowh-ai merged commit b97a212 into main Nov 25, 2024
6 checks passed
@kowh-ai kowh-ai deleted the build-push-actions-latest-tag branch November 25, 2024 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants