Open
Conversation
ronaldtse
added a commit
that referenced
this pull request
Feb 20, 2026
Delete all legacy {version}.yaml files from tool directories.
The register now uses ONLY the implementation-based format:
tools/{tool}/
├── index.yaml # Implementation index
└── {implementation}/ # Implementation directory
└── {version}.yaml # Version definition
This eliminates the confusion documented in PR #8 where developers
were editing the wrong file. There is now ONE format with no
ambiguity about which file is the source of truth.
Deleted: 83 legacy YAML files
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.
This document explains the confusion between legacy single-file definitions and v2 implementation version files.
Problem
When fixing the
batch_processdefault for Inkscape, I editedtools/inkscape/1.0.yamlbut the v2 loader usestools/inkscape/default/1.0.yaml. This caused the fix to not take effect.Solution
This PR adds documentation explaining:
Related: #7 (the fix for batch_process)