Make build-schema multi-project and improve template version handling#888
Merged
Conversation
…d fix schema template version history retrieval
This was
linked to
issues
May 26, 2026
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
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.
Summary
This PR extends
build-schemato support project-specific schema/template generation and improves how metadata template version history is handled.Changes
build-schemaproject-aware.--initial-versionhandling for first template releases.VERSIONhistory when a template is provided or found in assets.--initial-versionwith--excel_template.build-schema.Notes
Redlabra can now generate its own outputs, such as:
redlabra_schema.jsonredlabra_metadata_template_v*.xlsxPR Checklist
black and flake8).CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).