fix(ansible): bump default dagger module to v0.120.0 - #121
Merged
Conversation
The reusable ansible collection workflow defaulted to dagger/ansible@v0.13.0 and dagger v0.18.10, both long superseded. Callers that pass explicit values were unaffected, which is why this went unnoticed - stuttgart-things/ansible passes its own pins - but any caller relying on the defaults got a module over 100 versions old. v0.120.0 is the first version that derives galaxy.yml from collection.yaml instead of hardcoding the template, so collections built with the old default shipped placeholder metadata and declared GPL-2.0-or-later regardless of their actual license. dagger-version moves to v0.21.7 to match dagger.json engineVersion in the module and the value stuttgart-things/ansible already passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FDecVMyhtUtixsLmT4oLwY
patrick-hermann-sva
temporarily deployed
to
linting
July 28, 2026 11:23 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
33 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
call-ansible-collection.yamldefaulted todagger/ansible@v0.13.0anddagger 0.18.10. The module is at v0.120.0 — the default was over 100 versions behind.This stayed invisible because the only known caller,
stuttgart-things/ansible, passes its own explicit pins. Any caller relying on the defaults, though, got a module old enough to predate the metadata fix.v0.120.0is the first version that derivesgalaxy.ymlfromcollection.yamlinstead of hardcoding the template (stuttgart-things/dagger#320). Collections built with the old default shipped placeholder metadata and declaredGPL-2.0-or-laterregardless of their actual license.Changes
dagger-module-versionv0.13.0v0.120.0dagger-version0.18.10v0.21.7v0.21.7matchesengineVersionin the module'sdagger.jsonand the valuestuttgart-things/ansiblealready passes, so thevprefix is a format the action is known to accept in practice.Verification
Defaults only — no behaviour change for callers passing explicit values, which covers every known caller today.
v0.120.0was exercised end to end through this workflow at stuttgart-things/ansible#1044: all four collections built and released, and the published artifacts'MANIFEST.jsonnow readlicense: ["Apache-2.0"]with correct authors and tags, where every prior release saidGPL-2.0-or-later.YAML re-validated.
Related
@mainreference to this workflow🤖 Generated with Claude Code
https://claude.ai/code/session_01FDecVMyhtUtixsLmT4oLwY