You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The release date for version 1.25 is marked as "xx of February 2025". This placeholder should be replaced with the actual release date to ensure clarity and accuracy.
The changelog section for version 1.25 contains placeholders and lacks actual content. Ensure that the changelog is updated with specific details about the fixed issues, benefits, and customer impact as per the provided guidelines.
#### Changelog {#Changelog-v1.23.0}<!-- Required. The change log should include the following ordered set of sections below that briefly summarise the features, updates and fixed issues of the release.Here it is important to explain the benefit of each changelog item. As mentioned by James in a previous Slack message (https://tyktech.slack.com/archives/C044R3ZTN6L/p1686812207060839?thread_ts=1686762128.651249&cid=C044R3ZTN6L):"...it is important to document the customer impact for the work delivered, so we can share it with prospects/install base. For example:"New Chart delivers x and y benefit to a and b customer use cases. The business impact for them will be this and that" -->##### 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. -->
-#### Release Date xx of February 2025+#### Release Date 15th of February 2025
Suggestion importance[1-10]: 7
Why: Providing an exact release date improves clarity and avoids ambiguity for readers. While the suggestion is valid and enhances the documentation, it is not critical and could be addressed later if necessary.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
For internal users - Please add a Jira DX PR ticket to the subject!
Preview Link
Description
Screenshots (if appropriate)
Checklist
master.PR Type
Documentation
Description
Added release notes for version 1.25.
Included placeholders for highlights, breaking changes, and deprecations.
Provided a download link for the latest Mserv version.
Structured changelog section for fixed issues and customer impact.
Changes walkthrough 📝
cloud.md
Added release notes for version 1.25.tyk-docs/content/developer-support/release-notes/cloud.md