fix: fall back to dev schema for dev MEI versions#1357
Merged
Conversation
Member
Author
|
Merging as the broken link is due to cirmmt website is getting 502 error. |
yinanazhou
added a commit
that referenced
this pull request
May 2, 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.
Verovio was updated and now defaults to outputting
6.0-dev. When Neon tries to fetch the corresponding schema for validation, it constructs the URL using the mei version attribute. However, the music-encoding schema repository does not have a6.0-devfolder. The dev schema lives underdev/. This causes the fetch to 404, and Neon surfaces "Unknown MEI Version" to the user.Since there is no way to set the version Verovio outputs, the fix lives on the schema-fetching side in Neon.
fetchSchemanow tries the exact mei version value first. If that fetch fails and the version containsdev, it retries withdevas the schema folder. This preserves forward compatibility: if a future dev version gets its own dedicated folder on the schema repo, it will be used automatically; only versions without a matching folder fall back to dev.refs: #1356