[DX-1579] Add FIPS compliance to release notes for Pump 1.10 & Gatewa…

…y 5.3.3 (#5159) * add FIPS compliance to release notes for Pump & Gateway --------- Co-authored-by: Simon Pears <[email protected]>
TykTechnologies · Aug 2, 2024 · 20506fb · 20506fb
1 parent 20f027c
commit 20506fb
Show file tree

Hide file tree

Showing 2 changed files with 31 additions and 3 deletions.
diff --git a/tyk-docs/content/product-stack/tyk-gateway/release-notes/version-5.3.md b/tyk-docs/content/product-stack/tyk-gateway/release-notes/version-5.3.md
@@ -42,8 +42,14 @@ If you are using 5.3.0 we advise you to upgrade ASAP and if you are on an older
 
 
 ### Release Highlights
+
+#### Bug Fixes
+
 This release primarily focuses on bug fixes. For a comprehensive list of changes, please refer to the detailed [changelog]({{< ref "#Changelog-v5.3.3">}}) below.
 
+#### FIPS Compliance
+
+Tyk Gateway now offers [FIPS 140-2](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf) compliance. For further details please consult [Tyk API Management FIPS support]({{< ref "developer-support/special-releases-and-features/fips-release" >}}).
 
 ### Dependencies
 
@@ -102,6 +108,8 @@ Here it is important to explain the benefit of each changelog item. As mentioned
 "New Chart delivers x and y benefit to a and b customer use cases. The business impact for them will be this and that" -->
 
 #### Added
+
+
 <!-- This section should be a bullet point list of new features. Explain:
 
 - The purpose of the new feature
@@ -111,6 +119,14 @@ Here it is important to explain the benefit of each changelog item. As mentioned
 
 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. -->
 <ul>
+<li>
+<details>
+<summary>Added FIPS compliance</summary>
+
+Added [FIPS compliance]({{< ref "developer-support/special-releases-and-features/fips-release" >}}) for Tyk Gateway.
+</details>
+</li>
+
 <li>
 <details>
 <summary>Corrected ordering of OAS API paths to prevent middleware misapplication</summary>

diff --git a/tyk-docs/content/product-stack/tyk-pump/release-notes/pump-1.10.md b/tyk-docs/content/product-stack/tyk-pump/release-notes/pump-1.10.md
@@ -47,6 +47,10 @@ For users currently on v1.9.X, we strongly recommend promptly upgrading to the l
 
 ### Release Highlights
 
+#### FIPS Compliance
+
+Tyk Pump now offers [FIPS 140-2](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf) compliance. For further details please consult [Tyk API Management FIPS support]({{< ref "developer-support/special-releases-and-features/fips-release" >}})
+
 #### Security fixes
 This release focuses on improving security and compliance, enhancing integration capabilities, and ensuring robust performance in secure environments.
 
@@ -59,17 +63,25 @@ This release focuses on improving security and compliance, enhancing integration
 
 ### Changelog {#Changelog-v1.10.0}
 
-#### Changed
+#### Added
 
-Nothing
+<ul>
+<li>
+<details>
+<summary>Added FIPS compliance</summary>
+
+Added [FIPS compliance]({{< ref "developer-support/special-releases-and-features/fips-release" >}}) for Tyk Pump.
+</details>
+</li>
+</ul>
 
 
 #### Fixed
 
 <ul>
 <li>
 <details>
-<summary>Fixed: Tyk Pump Splunk Integration using http_proxy and https_proxy Environment Variables</summary>
+<summary>Fixed Tyk Pump Splunk Integration using http_proxy and https_proxy Environment Variables</summary>
 
 Resolved an issue where `http_proxy` and `https_proxy` environment variables were not being respected in the Tyk Pump pod for Splunk connections.