Skip to content

Conversation

@buger
Copy link
Member

@buger buger commented Nov 6, 2025

User description

Redis Supported version wording change (#877)


PR Type

Documentation


Description

  • Clarify Redis support wording for 5.3+

  • Preserve guidance for ≤5.2.x users


Diagram Walkthrough

flowchart LR
  doc["database-settings.mdx Redis section"] -- "update wording" --> clarity["5.3+ phrasing clarified"]
  doc -- "retain" --> legacy["≤5.2.x guidance unchanged"]
Loading

File Walkthrough

Relevant files
Documentation
database-settings.mdx
Refine Redis support phrasing by version                                 

planning-for-production/database-settings.mdx

  • Update phrasing to "Tyk 5.3 and later".
  • Keep ≤5.2.x Redis support line unchanged.
+1/-1     

@buger buger enabled auto-merge (squash) November 6, 2025 10:07
@buger buger merged commit 0ea3272 into release-5.8 Nov 6, 2025
3 checks passed
@buger buger deleted the merge/release-5.8/d34ad145cce05feec138c198f9cf89f7b383bdaf branch November 6, 2025 10:08
@github-actions
Copy link

github-actions bot commented Nov 6, 2025

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶

877 - Partially compliant

Compliant requirements:

  • Clarify Redis support wording for Tyk 5.3 and later.
  • Preserve/keep guidance for Tyk 5.2.x and earlier unchanged.
  • Apply change in planning-for-production/database-settings.mdx Redis section.

Non-compliant requirements:

Requires further human verification:

  • None
⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Wording Consistency

Ensure phrasing "Tyk 5.3 and later supports Redis 6.2.x, 7.0.x, and 7.2.x" matches product support policy and is consistently used across related docs/pages.

- Tyk 5.3 and later supports Redis 6.2.x, 7.0.x, and 7.2.x

@github-actions
Copy link

github-actions bot commented Nov 6, 2025

PR Code Suggestions ✨

No code suggestions found for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants