castopod. Upgrading Compose config to follow BC break introduced in Docker tag 1.15.0 (fixes #225) #226
skobkin
commented
Owner
- fixing upstream BC break in Docker image 1.15.0.
- fixing upstream BC break in Docker image 1.15.0.
skobkin
added the bug
label
skobkin
self-assigned this
skobkin
added 1 commit 2026-02-17 20:52:04 +03:00
castopod. Upgrading Compose config to follow BC break introduced in Docker tag 1.15.0 (fixes #225)
All checks were successful
ci/woodpecker/pr/validate Pipeline was successful
Details
skobkin
added 1 commit 2026-02-17 20:53:13 +03:00
castopod. Adding comment on min version to .env.dist (closes #225)
All checks were successful
ci/woodpecker/pr/validate Pipeline was successful
Details
skobkin
merged commit b154152ed9 into master
skobkin
deleted branch castopod_bc_break_fix
skobkin
referenced this pull request from a commit
Merge pull request 'castopod. Upgrading Compose config to follow BC break introduced in Docker tag 1.15.0 (fixes #225)' (#226) from castopod_bc_break_fix into master
No reviewers
Labels
No labels
WIP
bug
duplicate
enhancement
new stack
security
to be researched
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
skobkin/docker-stacks!226
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "castopod_bc_break_fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?