Skip to content

Commit e7f79ef

Browse files
sharadregotiJoanCamosTykexcieveletzya
authored
Added release notes for Tyk cloud (#5622)
* Added release notes for Tyk cloud --------- Co-authored-by: JoanCamosTyk <[email protected]> Co-authored-by: Artem Hluvchynskyi <[email protected]> Co-authored-by: Yaara <[email protected]>
1 parent 0a8022d commit e7f79ef

File tree

2 files changed

+207
-0
lines changed

2 files changed

+207
-0
lines changed

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

+199
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,199 @@
1+
---
2+
title: Tyk Cloud Release Notes
3+
date: xx
4+
description: "Release notes documenting updates, enhancements, and changes for Tyk Cloud"
5+
tags: ["Tyk Cloud", "Release notes", "v1.23", "1.23.0", "changelog"]
6+
---
7+
8+
## 1.23.0 Release Notes
9+
10+
### Release Date 14 of November 2024
11+
12+
### Release Highlights
13+
14+
This Tyk Cloud update introduces features that improve both flexibility in plugin management and user onboarding. Now, [Mserv]({{< ref "tyk-cloud/configuration-options/using-plugins/uploading-bundle" >}}), supports **multiple plugin bundles**, allowing greater customization and easier deployment of plugin configurations. Additionally, we added an **embedded product tour** to enhance the deployment experience, offering a guided walkthrough of Tyk Dashboard’s features, ideal for users familiarizing themselves with the platform during onboarding.
15+
16+
For a comprehensive list of improvements and fixes, please check the detailed [changelog]({{< ref "#Changelog-v1.23.0">}}) below.
17+
18+
### Breaking Changes
19+
<!-- Required. Use the following statement if there are no breaking changes, or explain if there are -->
20+
21+
There are no breaking changes in this release
22+
23+
### Downloads
24+
25+
- [latest version of Mserv](https://github.com/TykTechnologies/mserv/releases/latest)
26+
27+
### Deprecations
28+
<!-- Required. Use the following statement if there are no deprecations, or explain if there are -->
29+
There are no deprecations in this release
30+
31+
### Changelog {#Changelog-v1.23.0}
32+
<!-- 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.
33+
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):
34+
"...it is important to document the customer impact for the work delivered, so we can share it with prospects/install base. For example:
35+
"New Chart delivers x and y benefit to a and b customer use cases. The business impact for them will be this and that" -->
36+
37+
#### Added
38+
<!-- This section should be a bullet point list of new features. Explain:
39+
- The purpose of the new feature
40+
- How does the new feature benefit users?
41+
- Link to documentation of the new feature
42+
- For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info.
43+
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. -->
44+
45+
<ul>
46+
<li>
47+
<details>
48+
<summary>
49+
Contact form for POC requests on trial expiration
50+
</summary>
51+
A HubSpot contact form has been added in both Tyk Cloud and Dashboard to facilitate contacting Tyk for a Proof of Concept (PoC) when a trial expires. This new form makes it easier to connect with our team and explore further options once
52+
the trial period ends.
53+
</details>
54+
</li>
55+
56+
<li>
57+
<details>
58+
<summary>
59+
Support for bundles with multiple plugins
60+
</summary>
61+
Tyk Cloud now supports multiple plugins in a bundle, allowing users to manage and deploy various binaries for the same plugin bundle. This enhancement provides greater flexibility in plugin configuration and deployment using `mservctl`.
62+
within MServ.
63+
</details>
64+
</li>
65+
66+
<li>
67+
<details>
68+
<summary>
69+
Embedded product tour during deployment wait time
70+
</summary>
71+
An embedded interactive product tour has been added within the deployment screen to guide users through the Tyk Dashboard while they wait for their free trial on-boarding to complete. This tour provides an overview of key features, helping users explore what they can do on Tyk Cloud during their trial.
72+
</details>
73+
</li>
74+
75+
76+
77+
</ul>
78+
79+
#### Changed
80+
<!-- This should be a bullet-point list of updated features. Explain:
81+
- Why was the update necessary?
82+
- How does the update benefit users?
83+
- Link to documentation of the updated feature
84+
- For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info.
85+
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. -->
86+
87+
<ul>
88+
<li>
89+
<details>
90+
<summary>
91+
UX Improvement: Redirect to activity by API section from the monitoring page
92+
</summary>
93+
Users are now redirected to the "Activity by API" section in the Tyk Dashboard upon clicking on the Control Plane (CP) name within the Cloud Monitoring page. This update provides a more seamless
94+
transition for users needing detailed activity insights directly from the monitoring interface.
95+
</details>
96+
</li>
97+
98+
</ul>
99+
100+
#### Fixed
101+
<!-- This section should be a bullet point list that describes the issues fixed in the release. For each fixed issue explain:
102+
- What problem the issue caused
103+
- How was the issue fixed
104+
- 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
105+
- For OSS - Link to the corresponding issue if possible on GitHub to allow the users to see further info.
106+
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. -->
107+
108+
<ul>
109+
<li>
110+
<details>
111+
<summary>
112+
"Add Portal Deployment" widget hidden for team members
113+
</summary>
114+
The "Add Portal Deployment" widget on the Environment page is now hidden for team members, providing a cleaner and more tailored UI experience by limiting portal management options to authorized roles
115+
only.
116+
</details>
117+
</li>
118+
119+
<li>
120+
<details>
121+
<summary>
122+
"Delete User" button hidden for org admin on Org+Billing admin profiles
123+
</summary>
124+
The "Delete User" button for Org Admins has been hidden when viewing Org+Billing Admin profiles on the Teams page. Previously, Org Admins could see this button but would encounter an error message, "operation on this class is not permitted," when attempting deletion.
125+
</details>
126+
</li>
127+
128+
<li>
129+
<details>
130+
<summary>
131+
Standardized behavior for "Upgrade" and "Account & Billing" buttons
132+
</summary>
133+
The behavior for accessing the billing app through the 'Upgrade' and 'Account & Billing' buttons has been standardized. Previously, clicking the 'Upgrade' button opened the billing app in a new tab, while 'Account & Billing' opened it in the same tab. Now, both buttons open the billing app consistently in the same tab.
134+
</details>
135+
</li>
136+
137+
138+
<li>
139+
<details>
140+
<summary>
141+
Direct access to "/password-reset" page now accessible without redirect
142+
</summary>
143+
Fixed an issue where accessing the /password-reset page directly redirected users to the login page. Now, users can navigate directly to the /password-reset page without being redirected, providing a consistent experience for password-reset requests regardless of how the page is accessed.
144+
</details>
145+
</li>
146+
147+
<li>
148+
<details>
149+
<summary>
150+
Billing sidebar display corrected when no subscriptions are present
151+
</summary>
152+
We have resolved a display issue in the billing sidebar that occurred when no subscriptions were active. Now, the sidebar menu displays correctly regardless of subscription status, providing a consistent and clear UI for all users.
153+
</details>
154+
</li>
155+
156+
<li>
157+
<details>
158+
<summary>
159+
Fix for hybrid codes visibility logic to manage node data retention
160+
</summary>
161+
This update addresses a critical bug in the Hybrid nodes visibility logic, which previously retained all connected node data for the Hybrid Data Planes indefinitely. The fix ensures that we only contains records from the last 7 days. This enhancement improves system performance at all stages within the Tyk Cloud UI for organizations with Hybrid Data Planes, especially those with multiple connected gateways.
162+
163+
</details>
164+
</li>
165+
166+
<li>
167+
<details>
168+
<summary>
169+
Improve stability for paid customers
170+
</summary>
171+
We have enhanced separation between free-trial and paid deployments to improve resilience and stability.
172+
</details>
173+
</li>
174+
175+
176+
</ul>
177+
178+
#### Security Fixes
179+
<!-- 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:
180+
1. Dependency-tracked CVEs - External-tracked CVEs should be included on the release note.
181+
2. Internal scanned CVEs - Refer to the relevant engineering and delivery policy.
182+
For agreed CVE security fixes, provide a link to the corresponding entry on the NIST website. For example:
183+
- Fixed the following CVEs:
184+
- [CVE-2022-33082](https://nvd.nist.gov/vuln/detail/CVE-2022-33082)
185+
-->
186+
<ul>
187+
<li>
188+
<details>
189+
<summary>
190+
Bumped dependencies in Tyk Cloud components
191+
</summary>
192+
Dependencies across all Tyk Cloud components have been updated to address reported security issues. This update ensures compliance with security standards, aligning the project with best practices for secure dependency management.
193+
</details>
194+
</li>
195+
</ul>
196+
197+
198+
### FAQ
199+
Please visit our [Developer Support]({{< ref "frequently-asked-questions/faq" >}}) page for further information relating to reporting bugs, upgrading Tyk, technical support and how to contribute.

‎tyk-docs/data/menu.yaml

+8
Original file line numberDiff line numberDiff line change
@@ -4928,6 +4928,14 @@ menu:
49284928
path: /developer-support/backups/backup-apis-and-policies
49294929
category: Page
49304930
show: True
4931+
- title: "Release Notes"
4932+
category: Directory
4933+
show: True
4934+
menu:
4935+
- title: "Tyk Cloud"
4936+
path: /developer-support/release-notes/cloud
4937+
category: Page
4938+
show: True
49314939
- title: "Latest Tyk Releases"
49324940
path: /developer-support/tyk-release-summary/overview
49334941
category: Page

0 commit comments

Comments
 (0)