Cloud Release Notes 1.25.0.md

[JoanCamosTyk]

User description

For internal users - Please add a Jira DX PR ticket to the subject!

DX-1787https://tyktech.atlassian.net/browse/DX-1787(DX-1787)

---

Preview Link

Description

Screenshots (if appropriate)

Checklist

• I have added a preview link to the PR description.
• I have reviewed the suggestions made by our AI (PR Agent) and updated them accordingly (spelling errors, rephrasing, etc.)
• I have reviewed the guidelines for contributing to this repository.
• I have read the technical guidelines for contributing to this repository.
• Make sure you have started your change off our latest master.
• I labeled the PR

---

PR Type

Documentation

---

Description

• Added release notes for Tyk Cloud version 1.25.0.

• Included placeholders for breaking changes, deprecations, and changelog sections.

• Provided links for downloads and further information.

• Updated structure to align with release note standards.

---

Changes walkthrough 📝

	Relevant files
Documentation	cloud.md Added Tyk Cloud 1.25.0 release notes section                          tyk-docs/content/developer-support/release-notes/cloud.md Added a new section for version 1.25.0 release notes. Included placeholders for breaking changes, deprecations, and changelog. Added a download link for the latest version of Mserv. Updated FAQ section with a link to Developer Support. +65/-2

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Missing Content The Added, Changed, Fixed, and Security Fixes sections in the changelog for version 1.25.0 are placeholders and lack actual content. Ensure these sections are populated with relevant details before approval. ##### Added <!-- This section should be a bullet point list of new features. Explain: - The purpose of the new feature - How does the new feature benefit users? - Link to documentation of the new feature - For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info. Each change log item should be expandable. The first line summarises the changelog entry. It should be then possible to expand this to reveal further details about the changelog item. This is achieved using HTML as shown in the example below. --> ##### Changed <!-- This should be a bullet-point list of updated features. Explain: - Why was the update necessary? - How does the update benefit users? - Link to documentation of the updated feature - For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info. Each change log item should be expandable. The first line summarises the changelog entry. It should be then possible to expand this to reveal further details about the changelog item. This is achieved using HTML as shown in the example below. --> ##### Fixed <!-- This section should be a bullet point list that describes the issues fixed in the release. For each fixed issue explain: - What problem the issue caused - How was the issue fixed - Link to (new) documentation created as a result of a fix. For example, a new configuration parameter may have been introduced and documented for the fix - For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info. Each change log item should be expandable. The first line summarises the changelog entry. It should be then possible to expand this to reveal further details about the changelog item. This is achieved using HTML as shown in the example below. --> ##### Security Fixes <!-- This section should be a bullet point list that should be included when any security fixes have been made in the release, e.g. CVEs. For CVE fixes, consideration needs to be made as follows: 1. Dependency-tracked CVEs - External-tracked CVEs should be included on the release note. 2. Internal scanned CVEs - Refer to the relevant engineering and delivery policy. For agreed CVE security fixes, provide a link to the corresponding entry on the NIST website. For example: - Fixed the following CVEs: - [CVE-2022-33082](https://nvd.nist.gov/vuln/detail/CVE-2022-33082) --> Incomplete Release Highlights The Release Highlights section for version 1.25.0 is empty. This section should summarize the key updates or features introduced in the release. ### Release Highlights

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	01fd2ae
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/677e5d2a243a0c0008c26448
😎 Deploy Preview	https://deploy-preview-5877--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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