From f1ea2b21567e49fb2bc3690bf542d09340df457b Mon Sep 17 00:00:00 2001 From: Jonas Lagoni Date: Mon, 20 Nov 2023 11:48:19 -1000 Subject: [PATCH] Update migrations/migrate-to-version-6.md Co-authored-by: Dale Lane --- migrations/migrate-to-version-6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrations/migrate-to-version-6.md b/migrations/migrate-to-version-6.md index 8b40e815..c246cbdd 100644 --- a/migrations/migrate-to-version-6.md +++ b/migrations/migrate-to-version-6.md @@ -16,6 +16,6 @@ module.exports = { }; ``` -However, while the it's still a pre-release, the underlying schemas CAN contain breaking changes from version to version, up until the AsyncAPI specification is released. This means that one AsyncAPI document using v3 in the pre-release stage might be valid in `6.0.0`, but invalid in the `6.1.0`. This ONLY applies to pre-release schemas, and NOT regular ones that is set in stone. +However, while it's still a pre-release, the underlying schemas CAN contain breaking changes from version to version, up until the AsyncAPI specification is released. This means that one AsyncAPI document using v3 in the pre-release stage might be valid in `6.0.0`, but invalid in the `6.1.0`. This ONLY applies to pre-release schemas, and NOT regular ones that are set in stone. If you want to make sure you don't use a schema not released yet, you have to whitelist which versions you allow in your tool. \ No newline at end of file