Repository navigation
Next 5.1.0 - #220
Merged
Merged
Next 5.1.0#220
Conversation
…orm schemas. Every build ran update-metainfo.js through sync-version, which set the current release entry's date to today. A release machine running on a later day than the release commit left run.rosie.rosi.metainfo.xml modified, so test:all refused the quality-gate proof. Builds now leave an existing entry's date alone; a new version still gets today's date, and --redate changes it on request for release preparation. The Linux and Windows capability schemas missed the permissions for the commands added in this branch, so a Linux build regenerated linux-schema.json and also dirtied the tree. They are byte-identical to the desktop schema again, as they were before.
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.
No description provided.