chore: bump qase-robotframework to 6.0.0 for suite hierarchy fix

Restoring the full Robot Framework suite hierarchy changes the location
where reported test cases land in Qase, which can break existing
projects that were built against the old flattened layout. Bump the
major version and document the migration path.

Author: gibiw

qase-robotframework/changelog.md

@@ -1,3 +1,9 @@
+# qase-robotframework 6.0.0
+
+## Breaking changes
+
+- Robot Framework suite hierarchy is now preserved when reporting to Qase. Previously the reporter registered only the deepest (leaf) suite, so a test under `Tests > Account > Login` ended up in a flat `Login` suite in Qase. The reporter now sends the full nested path. Existing projects whose Qase suites were created against the old flattened behaviour may see test cases land in a new nested suite tree on the next run, which can result in duplicates or breakage of any manual reorganisation. Review your project's suite layout before upgrading. ([#486](https://github.com/qase-tms/qase-python/issues/486))
+
 # qase-robotframework 5.1.0
 
 ## What's new

qase-robotframework/docs/UPGRADE.md

@@ -1,5 +1,23 @@
 # Upgrade guides
 
+## From 5.x to 6.x
+
+### Suite hierarchy is preserved
+
+Prior to v6, the reporter registered each test under only the deepest (leaf) suite of its Robot Framework hierarchy. A test located in `Tests > Account > Login` ended up in a flat `Login` suite in Qase, with `Tests` and `Account` discarded.
+
+Starting with v6, the reporter sends the full nested suite path, so the same test now lands in `Tests / Account / Login` in Qase.
+
+Impact:
+
+- If you are starting from a clean Qase project, no action is required.
+- If your Qase project already has cases created against the old flattened layout (or you reorganised the tree manually), the next run will create cases in a new nested location, which can result in duplicates.
+
+To avoid duplicates, either:
+
+- accept the new hierarchy and remove or archive the old flat suites in Qase, or
+- pin annotated tests to the existing cases by setting the Qase ID on each `*** Test Cases ***` entry (see [usage docs](usage.md)).
+
 ## From 2.x to 3.x
 
 ### Execution

qase-robotframework/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qase-robotframework"
-version = "5.1.0"
+version = "6.0.0"
 description = "Qase Robot Framework Plugin"
 readme = "README.md"
 authors = [{name = "Qase Team", email = "support@qase.io"}]