Compare commits

...
Author SHA1 Message Date
moritz fea0471c26 chore: publish 2.3.0+2.6.0 release
continuous-integration/drone/tag Build is passing
continuous-integration/drone/push Build is failing
2026-09-15 01:19:09 +02:00
moritz de5a0b4ad6 Merge pull request 'adds maintenance and updates readme' (#15) from carla/vikunja:maintenance-update into main
continuous-integration/drone/push Build is failing
Reviewed-on: #15
2026-09-14 22:45:29 +00:00
moritz 7319a0f1ab Merge pull request 'chore(deps): update redis docker tag to v8.10.1' (#14) from renovate/redis-8.x into main
continuous-integration/drone/push Build is failing
Reviewed-on: #14
2026-09-14 22:45:04 +00:00
moritz 665feb1f8e Merge pull request 'chore(deps): update vikunja/vikunja docker tag to v2.6.0' (#13) from renovate/vikunja-vikunja-2.x into main
continuous-integration/drone/push Build is failing
Reviewed-on: #13
2026-09-14 22:44:44 +00:00
renovate-bot 3c5fd8645e chore(deps): update vikunja/vikunja docker tag to v2.6.0 2026-08-31 18:26:21 +00:00
carla 283a66d69c adds maintenance and updates readme 2026-08-26 12:05:31 +02:00
renovate-bot 25419a539f chore(deps): update redis docker tag to v8.10.1 2026-08-20 17:36:21 +00:00
3 changed files with 37 additions and 5 deletions
+32
View File
@@ -0,0 +1,32 @@
# Vikunja Recipe Maintenance
All contributions should be made via a pull request. This is to ensure a
certain quality and consistency, that others can rely on.
## Maintainer Responsibilities
A recipe maintainer has the following responsibilities:
- Respond to pull requests / issues within two weeks
- Make image security updates within a week
- Make image major updates every three months
In order to fullfill these responsibilities a recipe maintainer:
- Has to watch the repository (to get notifications)
- Needs to make sure renovate is configured properly
## Pull Requests
A pull request can be merged if it is approved by at least one maintainer. For
pull requests opened by a maintainer they need to be approved by another
maintainer. Even though it is okay to merge a pull request with one approval, it
is always better if all maintainers looked at the pull request and approved it.
## Become a maintainer
Everyone can apply to be a recipe maintainer:
1. Watch the repository to always get updates
2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
3. Once the pull request gets merged you will be added to the [vikunja maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/vikunja-maintainers).
4. Join the room [#cc-|-vikunja-maintenance:matrix.org](#cc-|-vikunja-maintenance:matrix.org) and chat to other maintainers.
+2 -2
View File
@@ -4,9 +4,9 @@
Organize everything, on all platforms
<!-- metadata -->
* **Maintainer**: Local-IT: [@moritz](https://git.coopcloud.tech/moritz), [@msimon](https://git.coopcloud.tech/simon), [@carla](https://git.coopcloud.tech/carla)
* **Category**: Apps
* **Status**: 0
* **Status**: `stable`
* **Image**: [`vikunja`](https://hub.docker.com/r/vikunja), 4, upstream
* **Healthcheck**: Almost
* **Backups**: Yes
+3 -3
View File
@@ -19,7 +19,7 @@ services:
max_attempts: 0
app:
image: vikunja/vikunja:2.3.0
image: vikunja/vikunja:2.6.0
environment:
- DOMAIN
- LOG_LEVEL
@@ -71,7 +71,7 @@ services:
- "traefik.http.middlewares.${STACK_NAME}-redirect.redirectregex.replacement=https://${DOMAIN}$${1}"
- "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
- "coop-cloud.${STACK_NAME}.version=2.2.0+2.3.0"
- "coop-cloud.${STACK_NAME}.version=2.3.0+2.6.0"
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT:-120}"
healthcheck:
test: ["CMD", "/healthcheck"]
@@ -81,7 +81,7 @@ services:
start_period: 1m
redis:
image: redis:8.8.0-alpine
image: redis:8.10.1-alpine
networks:
- internal