Add LTS flag to v26.0 release entry

[timothycoleman]

User description

Add 'lts' property to version v26.0 in repos.json

Description

Page previews

---

PR Type

Enhancement

---

Description

• Add LTS flag to v26.0 release entry in repos.json

• Mark version v26.0 as long-term support release

---

Diagram Walkthrough

flowchart LR
  repos["repos.json"] -- "add lts property" --> v26["v26.0 release entry"]
  v26 -- "lts: true" --> lts["LTS flag enabled"]

Loading

File Walkthrough

	Relevant files
Configuration changes	repos.json Add LTS flag to v26.0 release entry                                            import/repos.json Added "lts": true property to v26.0 release entry Marks v26.0 as a long-term support version Added trailing comma to startPage property for JSON formatting consistency +2/-1

---

[github-actions]

Docs Preview

• Status: ⏳ Creating preview…

[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 ✨

No code suggestions found for the PR.

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://lts.documentation-21k.pages.dev
  Changed pages: