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.
Previously the
date_added
field was automatically added to the registry the first time that the update.py script was run for that node. This was done by checking whether the registry already had thedate_added
field for the given node and adding one if it was missing.However, when executing the update.py script in the CI workflow, we read the registry from the
main
branch and apply the changes to thecurrent_registry
branch. This means that thedate_added
field is never added to themain
branch, which means that the update.py script re-adds thedate_added
field every time.This PR makes the
date_added
field into a manually added field that should be included when a new node is added. This adds another (very small) manual step when adding a new node but with the current CI configuration there's no good way to do this automatically anymore.I've also updated the schema so it should be obvious when the
date_added
information is missing. This means we won't forget to add this info when adding new nodes.