From f6322a618d342a1885f248c3973ed0a42f3b5f5f Mon Sep 17 00:00:00 2001 From: Mikalai Radchuk Date: Mon, 4 Dec 2023 15:06:48 +0000 Subject: [PATCH] Use special note markdown Signed-off-by: Mikalai Radchuk --- docs/drafts/upgrade-support.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/drafts/upgrade-support.md b/docs/drafts/upgrade-support.md index 9ec2cc863..a0410c9cb 100644 --- a/docs/drafts/upgrade-support.md +++ b/docs/drafts/upgrade-support.md @@ -33,7 +33,8 @@ In a future release, it is planned to remove the `ForceSemverUpgradeConstraints` OLM supports Semver to provide a simplified way for package authors to define compatible upgrades. According to the Semver standard, releases within a major version (e.g. `>=1.0.0 <2.0.0`) must be compatible. As a result, package authors can publish a new package version following the Semver specification, and OLM assumes compatibility. Package authors do not have to explicitly define upgrade edges in the catalog. -**Note:** Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades). +> [!NOTE] +> Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades). ### Upgrades within the major version zero