From ed93093818fd96f7c0043efc94054f30d09a1ec0 Mon Sep 17 00:00:00 2001 From: Nuno Maduro Date: Wed, 10 Jan 2024 12:25:08 +0000 Subject: [PATCH] docs: adjusts example --- support-policy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/support-policy.md b/support-policy.md index 42498c8..0c47ab5 100644 --- a/support-policy.md +++ b/support-policy.md @@ -15,9 +15,9 @@ Bug fixes will be available for outdated versions for a duration of two years fo | Pest 1 | >= PHP 7.3 | January 7, 2021 | March 20, 2025 Pest adheres to semantic versioning principles, where the version number `x.y.z` conveys the following information: -- When issuing bug fixes, the `z` number is incremented (e.g., 2.10.2 to 2.10.3). -- When adding new non-breaking features or improvements, the `y` number is incremented (e.g., 2.10.2 to 2.12.0). -- When introducing breaking changes, the `x` number is incremented (e.g., 2.10.2 to 3.0.0). +- When issuing bug fixes, the `z` number is incremented (e.g., 3.10.2 to 3.10.3). +- When adding new non-breaking features or improvements, the `y` number is incremented (e.g., 3.10.2 to 3.12.0). +- When introducing breaking changes, the `x` number is incremented (e.g., 3.10.2 to 4.0.0). As maintainers of testing frameworks, we take the matter of breaking changes very seriously. Therefore, we always attempt to deliver incredible and robust new features without causing any disruption to the community's test suites. This is precisely why upgrading from Pest 1 to Pest 2 merely required updating your composer.json file, and we assure you that the process will be just as seamless when Pest v3 is released.