Re-run the release workflow so that vikunja/vikunja:unstable docker image contains latest merges to main #635

Closed
opened 2025-11-01 21:00:49 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @whogben on GitHub (Sep 19, 2025).

Description

The current :unstable release seems to be from March?
https://github.com/go-vikunja/vikunja/actions/workflows/release.yml

Lots of good stuff since then that would be nice to see in :unstable docker tag, even if the :latest isn't updated at all.
(specifically I'm seeking the iOS/MacOS CalDAV integration fixes, but presumably there's more good stuff in there)

Which alternatives did you consider using instead?

I considered going to source and building it instead.

Originally created by @whogben on GitHub (Sep 19, 2025). ### Description The current :unstable release seems to be from March? https://github.com/go-vikunja/vikunja/actions/workflows/release.yml Lots of good stuff since then that would be nice to see in :unstable docker tag, even if the :latest isn't updated at all. (specifically I'm seeking the iOS/MacOS CalDAV integration fixes, but presumably there's more good stuff in there) ### Which alternatives did you consider using instead? I considered going to source and building it instead.
Author
Owner

@kolaente commented on GitHub (Sep 20, 2025):

The workflow you're referencing is not used since March. Please looks at the push date on docker hub.

Unstable is updated on every push to the main branch.

@kolaente commented on GitHub (Sep 20, 2025): The workflow you're referencing is not used since March. Please looks at the push date on docker hub. Unstable is updated on every push to the main branch.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#635