Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance: Switch to Zammad 5.4.0. #328

Merged
merged 1 commit into from
Mar 14, 2023
Merged

Maintenance: Switch to Zammad 5.4.0. #328

merged 1 commit into from
Mar 14, 2023

Conversation

mgruner
Copy link
Collaborator

@mgruner mgruner commented Mar 14, 2023

No description provided.

@mgruner mgruner requested a review from monotek March 14, 2023 10:22
@mgruner
Copy link
Collaborator Author

mgruner commented Mar 14, 2023

@monotek where does the previously used build version information -6 in 5.3.1-6 come from? I was not sure if something similar must be specified now.

@monotek
Copy link
Member

monotek commented Mar 14, 2023

The docker tag suffixes will be used if there are unversioned bugfixes merged to stable branch.

I got them from the available docker tags:
https://hub.docker.com/r/zammad/zammad-docker-compose/tags

New tags are also always availavble from the logs of the docker release github action, check "Docker tags" from the "Docker metadata action" step.

For example the newest develop image tag: https://github.com/zammad/zammad/actions/runs/4414249214/jobs/7735711122

But checking the docker registry for tags should be more straight forward :)

@monotek monotek merged commit e5b0fed into master Mar 14, 2023
@mgruner mgruner deleted the zammad-5.4 branch March 31, 2023 11:29
floriankessler pushed a commit to floriankessler/zammad-docker-compose that referenced this pull request Jan 5, 2024
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