Skip to content

Commit d1cef1f

Browse files
authored
Use special note markdown (#562)
Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
1 parent 5ae5404 commit d1cef1f

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/drafts/upgrade-support.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,8 @@ In a future release, it is planned to remove the `ForceSemverUpgradeConstraints`
3333

3434
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.
3535

36-
**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).
36+
> [!NOTE]
37+
> 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).
3738

3839
### Upgrades within the major version zero
3940

0 commit comments

Comments
 (0)