build(release): release 2.0.7 and bump to next development version

[github-actions]

User description

This PR contains the following changes:

1. Release version bump to 2.0.7.
2. Filtered resources (docs, JS) updated to reflect the release version.
3. Next development version bump after the release.

---

PR Type

Enhancement

---

Description

• Bump development version to 2.0.8-SNAPSHOT

• Update Maven and npm package version references

• Update release branch tracking to v2.0.7

---

Diagram Walkthrough

flowchart LR
  A["Current Version 2.0.6-SNAPSHOT"] -- "Release 2.0.7" --> B["Development Version 2.0.8-SNAPSHOT"]
  B -- "Update pom.xml" --> C["Maven Configuration"]
  B -- "Update README.md" --> D["Documentation & Installation"]
  B -- "Update releasebranch.txt" --> E["Release Branch Tracking"]

Loading

File Walkthrough

	Relevant files
Configuration changes	pom.xml Update Maven project version to 2.0.8-SNAPSHOT                      pom.xml Update project version from 2.0.6-SNAPSHOT to 2.0.8-SNAPSHOT Reflects the next development version after 2.0.7 release +1/-1      releasebranch.txt Update release branch tracking to v2.0.7                                  releasebranch.txt Update release branch reference from v2.0.5 to v2.0.7 Tracks the current release branch being worked on +1/-1
Documentation	README.md Update package version references in documentation              README.md Update Maven dependency version from 2.0.5 to 2.0.8-SNAPSHOT Update npm package installation command to use 2.0.8-SNAPSHOT version Ensures documentation reflects current development version +2/-2

---

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Use stable release in documentation In README.md, change the dependency version from the development snapshot 2.0.8-SNAPSHOT to the latest stable release 2.0.7. README.md [20-24] <dependency> <groupId>io.github.guacsec</groupId> <artifactId>trustify-da-api-model</artifactId> - <version>2.0.8-SNAPSHOT</version> + <version>2.0.7</version> </dependency> Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that user-facing documentation should recommend the latest stable release (2.0.7) rather than an unstable development -SNAPSHOT version, which is a best practice.	Medium
More