hotfix

[N6REJ]

User description

fixes files not going into a version subfolder

---

PR Type

Bug fix

---

Description

• Update bundle release version from 2025.11.30 to 2026.1.5

• Ensures files are organized in correct version subfolder structure

---

Diagram Walkthrough

flowchart LR
  A["build.properties<br/>bundle.release"] -- "version update" --> B["2026.1.5<br/>correct subfolder"]

Loading

File Walkthrough

	Relevant files
Configuration changes	build.properties Update bundle release version number                                          build.properties Update bundle.release version from 2025.11.30 to 2026.1.5 Fixes version subfolder organization issue +1/-1

---

[qodo-code-review]

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]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Zero‐pad month and day in version Standardize the release version format by using two digits for the month and day (e.g., 2026.01.05) to maintain consistency with the previous pattern. build.properties [2] -bundle.release = 2026.1.5 +bundle.release = 2026.01.05 Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly points out that the new version format 2026.1.5 is inconsistent with the previous format 2025.11.30. Enforcing a consistent YYYY.MM.DD format improves readability and prevents potential sorting or parsing issues.	Low
More