Repository navigation
chore: datamodels-toolkit v0.3.15 - #14
Merged
Merged
Conversation
Signed-off-by: Daniel Kastl <daniel.kastl@gmail.com>
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.
Moves the node to datamodels-toolkit v0.3.15 with
datamodels upgrade: the workflow pins the v0.3.15 release of the Action (19a4018), and the Markdown files runnpx @geolonia/datamodels@0.3.15.What changes for a node (0.3.15):
node.yamlcan have an optionaltitleanddescription(a text per language). The pages use the title as the site's name, andcatalog.jsonlists both. Without them, nothing changes.exportandextendfind a model by its type IRI on the node that made it.nodesandextends[].indexmust be https URLs (this node already uses https only).check(offline and online) andbuildpass with 0.3.15. Every changed line only swaps the version or the commit.