Skip to content

Merging to release-5.8: Update cloud 1.28.1.md (#6487) #6489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

buger
Copy link
Member

@buger buger commented Jun 3, 2025

User description

Update cloud 1.28.1.md (#6487)

  • Update cloud 1.28.1.md

  • Update cloud.md

  • Update cloud 1.28.1.md


PR Type

Documentation


Description

  • Added release notes section for Tyk Cloud v1.28.1

  • Included release date, highlights, and changelog structure

  • Noted absence of breaking changes and deprecations

  • Provided download link for latest Mserv version


Changes walkthrough 📝

Relevant files
Documentation
cloud.md
Add 1.28.1 release notes and changelog section                     

tyk-docs/content/developer-support/release-notes/cloud.md

  • Introduced new section for 1.28.1 release notes
  • Added release date, highlights, and changelog structure
  • Noted absence of breaking changes and deprecations
  • Linked to latest Mserv release download
  • +71/-2   

    Need help?
  • Type /help how to ... in the comments thread for any questions about PR-Agent usage.
  • Check out the documentation for more information.
  • * Update cloud 1.28.1.md
    
    * Update cloud.md
    
    * Update cloud 1.28.1.md
    
    (cherry picked from commit d9308c4)
    @buger buger enabled auto-merge (squash) June 3, 2025 12:06
    Copy link
    Contributor

    github-actions bot commented Jun 3, 2025

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    🎫 Ticket compliance analysis ✅

    6487 - Fully compliant

    Compliant requirements:

    • Add a release notes section for Tyk Cloud version 1.28.1
    • Include release date and highlights placeholders
    • State no breaking changes or deprecations
    • Provide download link for latest Mserv version
    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Documentation Accuracy

    Ensure that the release notes accurately reflect the actual changes in Tyk Cloud v1.28.1 and that all described improvements and fixes are correct and not misleading.

    ## 1.28.1 Release Notes
    
    ### Release Date 03 June 2025
    
    ### Release Highlights
    
    This release improves Tyk Cloud’s security, scalability, and reliability. We’ve hardened the signup and login flows, improved sensitive data handling in API responses, and enhanced Redis scalability in Control Plane deployments to support larger workloads.
    
    For a full list of changes, see the detailed [changelog]({{< ref "#Changelog-v1.28.1" >}}) below.
    
    ### Breaking Changes
    
    There are no breaking changes in this release.
    
    ### Downloads
    - [latest version of Mserv](https://github.com/TykTechnologies/mserv/releases/latest)
    
    ### Deprecations
    
    There are no deprecations in this release.
    
    ### Changelog {#Changelog-v1.28.1}
    
    #### Added
    
    <ul>
    <li>
    <details>
    <summary>Improved scalability for Redis in Control Plane Deployments</summary>
    
    The change brings more flexible Redis scaling capabilities in the Control Plane deployments. Control Planes are now able to handle more/larger API keys in storage without causing stability issues. Tyk Cloud will expand this storage using this capability when needed, but a permanent arrangement is subject to commercial terms.
    
    </details>
    </li> 
    </ul>
    
    #### Fixed
    
    <ul>
    <li>
    <details>
    <summary>Hardened Signup Flow Validation</summary>
    
    Improved the signup logic to prevent unintended automation and ensure tighter control over account creation, enhancing platform security and reliability.
    
    </details>
    </li> 
    </ul>
    
    <ul>
    <li>
    <details>
    <summary>Consistent Login Response Behavior</summary>
    
    Standardized response status codes in the login process to prevent discrepancies that could lead to information exposure through http status code.
    
    </details>
    </li> 
    </ul>
    
    <ul>
    <li>
    <details>
    <summary>Sanitized Sensitive Data in API Responses</summary>
    
    Resolved an issue where certain sensitive fields could be inadvertently included in API responses. The platform now enforces stricter data handling and output sanitization.
    
    </details>
    </li> 
    </ul>

    Copy link
    Contributor

    github-actions bot commented Jun 3, 2025

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    Copy link

    netlify bot commented Jun 3, 2025

    PS. Add to the end of url /docs/nightly

    Name Link
    🔨 Latest commit a6fb1ef
    🔍 Latest deploy log https://app.netlify.com/projects/tyk-docs/deploys/683ee53e00a02400085e89ed
    😎 Deploy Preview https://deploy-preview-6489--tyk-docs.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

    To edit notification comments on pull requests, go to your Netlify project configuration.

    1 similar comment
    Copy link

    netlify bot commented Jun 3, 2025

    PS. Add to the end of url /docs/nightly

    Name Link
    🔨 Latest commit a6fb1ef
    🔍 Latest deploy log https://app.netlify.com/projects/tyk-docs/deploys/683ee53e00a02400085e89ed
    😎 Deploy Preview https://deploy-preview-6489--tyk-docs.netlify.app
    📱 Preview on mobile
    Toggle QR Code...

    QR Code

    Use your smartphone camera to open QR code link.

    To edit notification comments on pull requests, go to your Netlify project configuration.

    @buger buger merged commit 416c2e9 into release-5.8 Jun 3, 2025
    11 checks passed
    @buger buger deleted the merge/release-5.8/d9308c435754c939e2eb63fc5218d577528c17bc branch June 3, 2025 12:14
    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.

    2 participants