Skip to content
This repository was archived by the owner on Sep 9, 2025. It is now read-only.

Conversation

@bjhargrave
Copy link
Contributor

To prepare for future updates to the schema, we use a versioned folder. Then downstream users, such as cli, can use the schema file from the versioned folder(s) which the user understands. This will also allow users to support and validate documents from older schema versions.

We also add the version property to the schema. This is supported by cli from instructlab/instructlab#417. The version property is not required for version 1.

Copy link
Member

@hickeyma hickeyma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good @bjhargrave. Just some small nits.

Copy link
Member

@hickeyma hickeyma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @bjhargrave

To prepare for future updates to the schema, we use a versioned folder.
Then downstream users, such as cli, can use the schema file from the
versioned folder(s) which the user understands. This will also allow
users to support and validate documents from older schema versions.

We also add the version property to the schema. This is supported by
cli from instructlab/instructlab#417. The version
property is not required for version 1.

Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
Signed-off-by: BJ Hargrave <hargrave@us.ibm.com>
@bjhargrave bjhargrave merged commit 77a1f5e into instructlab:main Mar 28, 2024
@bjhargrave bjhargrave deleted the schema-versioning branch March 28, 2024 16:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants