Skip to content

🤖 Auto-merge documentation from branches - #2987

Merged
buger merged 1 commit into
productionfrom
docs-merge-1183
Sep 9, 2026
Merged

🤖 Auto-merge documentation from branches#2987
buger merged 1 commit into
productionfrom
docs-merge-1183

Conversation

@buger

@buger buger commented Sep 9, 2026

Copy link
Copy Markdown
Member

User description

📚 Documentation Merge Summary

This PR contains automatically merged documentation from multiple branches.

Triggered by:

Deployment Details:

  • Generated from: branches-config.json
  • Run ID: 34344148266
  • Subfolder: (root deployment)
  • Timestamp: $(date)

Changes Include:

  • ✅ Merged documentation from multiple branches
  • ✅ Generated unified docs.json configuration
  • ✅ Updated assets and content structure
  • ✅ Cleaned up outdated version folders

🚦 This PR will be processed by merge queue to ensure proper validation and ordering.

Previous deployment PRs have been automatically closed to prevent conflicts.


PR Type

Documentation


Description

  • Clarify legacy session lifecycle fallback conditions

  • Explain action and grace period interactions

  • Synchronize guidance across root and nightly docs


Diagram Walkthrough

flowchart LR
  old["Older Tyk version"]
  unset["Action is unset"]
  zero["Retain with zero grace"]
  legacy["Legacy session controls"]
  old -- "falls back to" --> legacy
  unset -- "falls back to" --> legacy
  zero -- "falls back to" --> legacy
Loading

File Walkthrough

Relevant files
Documentation
session-lifecycle.mdx
Clarify legacy session lifecycle fallback conditions         

api-management/access-control/sessions-and-keys/session-lifecycle.mdx

  • Enumerates three legacy fallback scenarios
  • Clarifies post_expiry_grace_period requires retain
  • Documents zero-grace retained-session behavior
  • Adds the missing final newline
+6/-2     
session-lifecycle.mdx
Synchronize nightly legacy session lifecycle guidance       

nightly/api-management/access-control/sessions-and-keys/session-lifecycle.mdx

  • Mirrors the three legacy fallback scenarios
  • Clarifies post_expiry_grace_period requires retain
  • Documents zero-grace retained-session behavior
  • Adds the missing final newline
+6/-2     

Generated from branches-config.json at

- Merged documentation from multiple branches
- Generated unified docs.json
- Updated assets and content structure
@buger buger added auto-deployment automated documentation Improvements or additions to documentation labels Sep 9, 2026
@mintlify

mintlify Bot commented Sep 9, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
tyk 🟢 Ready View Preview Sep 9, 2026, 11:22 AM

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅

2986 - PR Code Verified

Compliant requirements:

  • Clarify the three conditions that trigger legacy session lifetime controls.
  • Explain that post_expiry_grace_period applies only when post_expiry_action is set to retain.
  • Document that retain with a zero grace period uses legacy behavior.
  • Preserve the OAuth token expiration reference.

Requires further human verification:

  • Confirm that the automated merge and deployment target the release-5.15 documentation as intended.

2985 - Fully compliant

Compliant requirements:

  • Clarify the three conditions that trigger legacy session lifecycle controls.
  • Explain when post_expiry_grace_period takes effect.
  • Document the legacy behavior for retained sessions with a zero grace period.
⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ No major issues detected

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

PR Code Suggestions ✨

No code suggestions found for the PR.

@buger
buger merged commit e8350ad into production Sep 9, 2026
5 checks passed
@buger
buger deleted the docs-merge-1183 branch September 9, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant