Skip to content
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

[DX-1781] Release notes for 5.3.9 #5826

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

[DX-1781] Release notes for 5.3.9 #5826

wants to merge 9 commits into from

Conversation

Eopayemi
Copy link
Contributor

@Eopayemi Eopayemi commented Dec 16, 2024

User description

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

DX-1781

Preview Link

Description

Release notes for 5.3.9

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 comprehensive release notes for Tyk Dashboard and Gateway version 5.3.9.
  • Included compatibility matrices for Tyk components and third-party dependencies.
  • Detailed changelog sections for added features and fixed issues.
  • Provided upgrade instructions and download links for Docker images, Helm charts, and source code tarball.

Changes walkthrough 📝

Relevant files
Documentation
dashboard.md
Added detailed release notes for Tyk Dashboard version 5.3.9.

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

  • Added release notes for version 5.3.9, including highlights,
    dependencies, and upgrade instructions.
  • Included compatibility matrix for Tyk components and third-party
    dependencies.
  • Added changelog sections for added features and fixed issues.
  • Provided download links for Docker images and Helm charts.
  • +96/-0   
    gateway.md
    Added detailed release notes for Tyk Gateway version 5.3.9.

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

  • Added release notes for version 5.3.9, including highlights,
    dependencies, and upgrade instructions.
  • Included compatibility matrix for Tyk components and third-party
    dependencies.
  • Added changelog sections for added features and fixed issues.
  • Provided download links for Docker images, Helm charts, and source
    code tarball.
  • +101/-0 

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

    Copy link
    Contributor

    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

    Documentation Clarity
    Ensure that the placeholders like "Release Date xxx" and "Add changelog summary" are replaced with actual content before merging. These placeholders could confuse users if left unresolved.

    Documentation Clarity
    Verify that placeholders such as "Release Date xxx" and "Add changelog summary" are updated with accurate information to maintain professionalism and clarity in the release notes.

    Copy link
    Contributor

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    Copy link

    netlify bot commented Dec 16, 2024

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

    Name Link
    🔨 Latest commit e4cbc5a
    🔍 Latest deploy log https://app.netlify.com/sites/tyk-docs/deploys/6762f459b9c610000885b17c
    😎 Deploy Preview https://deploy-preview-5826--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 site configuration.

    #### Release Date xxx

    #### Release Highlights
    This release contains a bug fix. For a comprehensive list of changes, please refer to the detailed [changelog]({{< ref "#Changelog-v5.3.9">}}) below.
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    This release contains a bug fix. For a comprehensive list of changes, please refer to the detailed [changelog]({{< ref "#Changelog-v5.3.9">}}) below.
    This release contains bug fixes. For a comprehensive list of changes, please refer to the detailed [changelog]({{< ref "#Changelog-v5.3.9">}}) below.

    Given the time difference between your upgrade and the release of this version, we recommend customers verify the ongoing support of third-party dependencies they install, as their status may have changed since the release.

    #### Deprecations
    We have deprecated 'http_server_options.prefer_server_ciphers' in Tyk dashboard due due to its obsolescence in upstream dependencies.Users are advised to remove this configuration from their setups as it will no longer have any effect in future releases.
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    We have deprecated 'http_server_options.prefer_server_ciphers' in Tyk dashboard due due to its obsolescence in upstream dependencies.Users are advised to remove this configuration from their setups as it will no longer have any effect in future releases.
    We have deprecated the obsolescent `http_server_options.prefer_server_ciphers` configuration option. This legacy control no longer has any effect on the underlying library and users are advised to remove this setting from their configurations.

    <ul>
    <li>
    <details>
    <summary>Duplicate text in hint box for path-based permissions</summary>
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    I don't think this needs to be picked out in the change log - it's a very minor UI bug fix that has no impact on users. I would leave it out.

    </li>
    <li>
    <details>
    <summary>Blank screen on restore zoom in API activity dashboard</summary>
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    What do we mean by "restore zoom"?

    </li>
    <li>
    <details>
    <summary>Search icon non-responsive on keys page</summary>
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    <summary>Search icon non-responsive on keys page</summary>
    <summary>Search icon unresponsive on API Keys page</summary>

    <details>
    <summary>SSE streaming reliability enhanced</summary>

    Fixed an issue where upstream server-sent events (SSE) were not sent when OpenTelemetry was enabled.Resolved a gateway panic triggered when detailed recording was enabled and upstream sent SSE.
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    From my reading of the ticket, the issue was that the Gateway would panic (crash) - probably worth checking with @jeffy-mathew, as the release note on the ticket does mention two fixes, but the ticket description only mentions the panic.

    </li>
    <li>
    <details>
    <summary>OAuth 2.0 token issuance now supported in Emergency mode</summary>
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    I don't see "Emergency Mode" anywhere in the docs - so would recommend something like:

    Suggested change
    <summary>OAuth 2.0 token issuance now supported in Emergency mode</summary>
    <summary>Fixed an issue where OAuth 2.0 access tokens would not be issued if the data plane was disconnected from the control plane</summary>

    <details>
    <summary>OAuth 2.0 token issuance now supported in Emergency mode</summary>

    OAuth 2.0 tokens can now be issued even when data plane gateways are in emergency mode. This is achieved by saving OAuth clients locally when they are pulled from RPC.
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Suggested change
    OAuth 2.0 tokens can now be issued even when data plane gateways are in emergency mode. This is achieved by saving OAuth clients locally when they are pulled from RPC.
    OAuth 2.0 access tokens can now be issued even when data plane gateways are disconnected from the control plane. This is achieved by saving OAuth clients locally within the data plane when they are pulled from RPC.

    </li>
    <li>
    <details>
    <summary>Request size limit Middleware no longer breaks GET or DELETE requests</summary>
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    "Breaks" is a bit vague - I would suggest something like:

    Suggested change
    <summary>Request size limit Middleware no longer breaks GET or DELETE requests</summary>
    <summary>Request size limit middleware would block any request without a payload (for example GET, DELETE)</summary>

    <details>
    <summary>Request size limit Middleware no longer breaks GET or DELETE requests</summary>

    Resolved a problem where the request size limit middleware was incorrectly breaking GET and DELETE requests.
    Copy link
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    I think we can explain here that the middleware would expect to see a request body (payload) and fail validation if none was found, effectively blocking GET and DELETE methods.

    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.

    3 participants