Update supported version in SECURITY.md

[kimkulling]

• Preparation for bugfix release v6.0.5

Summary by CodeRabbit

• Documentation
  • Updated security guidance to reference the latest supported version.
• Chores
  • Project version updated to the new release number.
• Tests
  • Unit test expectations updated to align with the new version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e951318 and 3f415c2.

📒 Files selected for processing (2)

• CMakeLists.txt
• test/unit/utVersion.cpp

---

📝 Walkthrough

Walkthrough

Bumped project and patch versions across documentation, build config, and a unit test: updated SECURITY.md supported security version to 6.0.5, changed PROJECT version in CMakeLists.txt to 6.0.5, and adjusted unit test expectation in test/unit/utVersion.cpp from 4 to 5.

Changes

Cohort / File(s)	Summary
Security Documentation SECURITY.md	Updated supported security version in the compatibility table from 6.0.2 to 6.0.5 (documentation-only change).
Build Configuration CMakeLists.txt	Updated top-level PROJECT(...) version from 6.0.4 to 6.0.5 (version metadata change).
Unit Tests test/unit/utVersion.cpp	Adjusted unit test expectation (aiGetVersionPatchTest) from 4U to 5U to match new project patch version.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update copyright year and project version #6454 — Also updates project version and corresponding unit test patch expectation in CMakeLists.txt and test/unit/utVersion.cpp.

Suggested labels

Build

Poem

🐰 A tiny hop, a tidy tweak,
Versions aligned — no mystery to seek,
Docs and build and tests in tune,
I nibble carrots, hum a tune. 🥕✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title only describes updating SECURITY.md, but the changeset also modifies CMakeLists.txt and test files for a version bump to 6.0.5.	Update the title to reflect the complete scope, such as 'Prepare for v6.0.5 bugfix release' or 'Bump version to 6.0.5 across project files'.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/update_bugfix_release

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@SECURITY.md`:
- Line 9: SECURITY.md was bumped to 6.0.5 but the source version tokens were not
updated; update the version declaration in the CMake project (the project(...)
or PROJECT_VERSION variable in CMakeLists.txt currently set to 6.0.4) to 6.0.5
and update the package version string in the PyAssimp pyproject metadata (the
version = "6.0.2" entry in pyproject.toml) to 6.0.5 so all version references
are consistent.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud