docs: add Package and Container Image Retention Policy

[probelabs]

User description

Problem / Task

Create a new docs page for "Package and Container Image Retention Policy" as requested in Slack.

Requested by: UHNSF8FHN
Slack thread: https://tyktech.slack.com/archives/D0A06TD1B3L/p1787216096363519

Changes

• Created developer-support/retention-policy.mdx with the new policy text.
• Added the new page to docs.json under the "Releases Policy" group.
• Added <Note> callouts to tyk-self-managed/install/linux.mdx and tyk-self-managed/install/docker.mdx linking to the new policy.

Testing

• Verified the MDX formatting.
• Verified docs.json syntax is valid.

---

Trace: 817d332453095566dee616197fda4be4
Generated with Visor AI Assistant

---

PR Type

Documentation

---

Description

• Add retention policy reference page

• Define edition-specific pruning windows

• Document notice timelines and opt-in

• Link policy from install docs

---

Diagram Walkthrough

flowchart LR
  policy["New retention policy page"]
  nav["Releases Policy navigation"]
  linux["Linux install documentation"]
  docker["Docker install documentation"]
  nav -- "adds page entry" --> policy
  linux -- "links to" --> policy
  docker -- "links to" --> policy

Loading

File Walkthrough

Relevant files

Documentation

retention-policy.mdx New retention policy reference documentation                          developer-support/retention-policy.mdx Add a new policy page for package and image retention Explain retention rules for CE, EE, and FIPS editions Document pruning triggers, grace periods, and notice timelines Include guidance for opt-in notices and upgrade planning +108/-0  docs.json Register retention policy in docs nav                                        docs.json Add developer-support/retention-policy to the Releases Policy group Make the new policy page discoverable in docs navigation +2/-1      docker.mdx Link Docker install docs to policy                                              tyk-self-managed/install/docker.mdx Add a Note linking Docker installers to the retention policy Clarify container image lifecycle guidance before installation +4/-0      linux.mdx Link Linux install docs to policy                                                tyk-self-managed/install/linux.mdx Add a Note linking Linux installers to the retention policy Clarify package lifecycle guidance before installation +4/-0

---

[probelabs]

This PR introduces a new documentation page for the "Package and Container Image Retention Policy". This policy formalizes the lifecycle for Tyk's software artifacts (DEB/RPM packages and Docker images), clarifying how long older versions will remain available in public registries. The new page is also added to the documentation site's navigation.

Files Changed Analysis

• developer-support/retention-policy.mdx: A new documentation page (+107 lines) has been added. It details the retention policy, including the rationale, a pruning start date of 1st December 2026, and distinct retention windows for Community Edition (CE) and Enterprise Edition (EE) packages.
• docs.json: The site's navigation configuration has been updated (+2/-1 lines) to include the new retention policy page under the "Releases Policy" group, making it discoverable for users browsing the documentation.

Architecture & Impact Assessment

• What this PR accomplishes: It establishes and communicates a formal policy for software artifact retention. This provides clarity and predictability for users, helping them plan upgrades and maintain secure, supported deployments.
• Key technical changes introduced: The changes are purely documentary. They involve adding a new Markdown file and updating a JSON configuration file for navigation. There are no code changes.
• Affected system components: The primary impact is on the user-facing documentation. This change directly affects administrators and operators of self-managed Tyk deployments, as the policy governs the availability of the installation packages and container images they use.

graph TD
    A["New Policy Page<br>(developer-support/retention-policy.mdx)"]
    B["Navigation Config<br>(docs.json)"]
    B --|Adds link to|--> A

Loading

Scope Discovery & Context Expansion

• The scope of this change is confined to the documentation repository and does not involve any changes to the application code or infrastructure.
• Discrepancy: The PR description states that links to the new policy were added to the Linux and Docker installation guides (tyk-self-managed/install/linux.mdx and tyk-self-managed/install/docker.mdx), but these changes are not present in the provided diff. This is a key point to address during review to ensure the policy is easily discoverable by users during the installation process.

Metadata

• Review Effort: 1 / 5
• Primary Label: documentation

---

Powered by Visor from Probelabs

Last updated: 2026-08-26T14:15:40.821Z | Triggered by: pr_updated | Commit: 1ca7f79

💡 TIP: You can chat with Visor using /visor ask <your question>

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

Quality Issues (1)

Severity	Location	Issue
🟡 Warning	developer-support/retention-policy.mdx:1	The pull request description and its 'File Walkthrough' section state that links to the new retention policy page were added to `tyk-self-managed/install/linux.mdx` and `tyk-self-managed/install/docker.mdx`. However, these changes are missing from the actual diff provided for review. This omission significantly reduces the discoverability of the new policy for users during the installation process. 💡 Suggestion Include the changes to `tyk-self-managed/install/linux.mdx` and `tyk-self-managed/install/docker.mdx` in this pull request to ensure the new retention policy is properly linked and visible to users.

---

Powered by Visor from Probelabs

Last updated: 2026-08-26T14:15:32.121Z | Triggered by: pr_updated | Commit: 1ca7f79

💡 TIP: You can chat with Visor using /visor ask <your question>

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.