Skip to content

Conversation

@ilijabojanovic
Copy link
Member

Description

Related Issue

Motivation and Context

Test Coverage For This Change

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Refactoring or add test (improvements in base code or adds test coverage to functionality)
  • Documentation updates or improvements.

Checklist

  • Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If PRing from your fork, don't come from your master!
  • Make sure you are making a pull request against our master branch (left side). Also, it would be best if you started your change off our latest master.
  • My change requires a change to the documentation.
    • I have manually updated the README(s)/documentation accordingly.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@ilijabojanovic ilijabojanovic requested a review from a team as a code owner December 19, 2025 14:57
@probelabs
Copy link

probelabs bot commented Dec 19, 2025

This pull request introduces the 5.0.0 major release for the Tyk Helm charts. The changes involve a consistent version bump across all charts and an update to the default image tags for the underlying Tyk components.

Files Changed Analysis

  • Total Files Changed: 21
  • Additions/Deletions: 56 additions, 56 deletions
  • Key Patterns: The changes are highly consistent and mechanical across the repository:
    • All Chart.yaml files for both umbrella and component charts have their version updated from 4.1.1 to 5.0.0.
    • The corresponding Chart.lock files in umbrella charts (tyk-control-plane, tyk-data-plane, tyk-oss, tyk-stack) are updated to reflect the new 5.0.0 dependency versions.
    • values.yaml files are updated with new image tags for Tyk services:
      • Tyk Dashboard: v5.8.8v5.8.9
      • Tyk Dev Portal: v1.15.0v1.16.0
      • Tyk Gateway: v5.8.8v5.8.9
      • Tyk MDCB: v2.8.6v2.8.7
      • Tyk Pump: v1.13.1v1.13.2

Architecture & Impact Assessment

  • What this PR accomplishes: This PR formalizes a major version release (5.0.0) for the entire suite of Tyk Helm charts, ensuring that users deploying a new installation or upgrading will receive the latest versions of all Tyk components.
  • Key technical changes introduced: The core changes are updating version metadata in Helm chart definitions and default image tags in values.yaml files.
  • Affected system components: This is a global change affecting all Tyk deployments managed by these charts, including tyk-stack, tyk-control-plane, tyk-data-plane, and tyk-oss. The update impacts every core service, from the gateway to the dashboard.

Component Dependencies

The following diagram illustrates the relationship between the umbrella charts and the component charts being updated.

graph TD
    subgraph Umbrella Charts
        A[tyk-stack]
        B[tyk-control-plane]
        C[tyk-data-plane]
        D[tyk-oss]
    end

    subgraph Component Charts
        E[tyk-gateway]
        F[tyk-dashboard]
        G[tyk-pump]
        H[tyk-bootstrap]
        I[tyk-dev-portal]
        J[tyk-mdcb]
    end

    A --> E & F & G & H & I
    B --> E & F & G & H & I & J
    C --> E & G
    D --> E & G
Loading

Scope Discovery & Context Expansion

  • The scope of this PR is repository-wide, touching all published charts to ensure a synchronized release. While the diff itself is simple, it represents a significant release milestone.
  • The primary impact lies within the updated container images. A thorough review should extend beyond this PR to include validating the release notes for each updated component (e.g., Tyk Gateway v5.8.9, Dev Portal v1.16.0) to understand the features, fixes, and potential breaking changes introduced in this new version.
Metadata
  • Review Effort: 2 / 5
  • Primary Label: chore

Powered by Visor from Probelabs

Last updated: 2025-12-19T15:02:27.771Z | Triggered by: pr_updated | Commit: 7ba0e58

💡 TIP: You can chat with Visor using /visor ask <your question>

@probelabs
Copy link

probelabs bot commented Dec 19, 2025

Security Issues (1)

Severity Location Issue
🟡 Warning tyk-control-plane/values.yaml:342-1797
This PR updates multiple container image tags across various `values.yaml` files (e.g., `tyk-gateway` to `v5.8.9`, `tyk-dashboard` to `v5.8.9`, `tyk-dev-portal` to `v1.16.0`, etc.). While dependency updates are necessary for security and functionality, they also carry the risk of introducing new vulnerabilities. The security posture of these new image versions has not been verified.
💡 SuggestionIntegrate a container vulnerability scanner (e.g., Trivy, Clair, Snyk) into the CI/CD pipeline to automatically scan new image versions for known CVEs before they are deployed. As a manual step for this PR, the release notes for each updated component should be reviewed for any security-related fixes or disclosures, and the images should be scanned.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ Quality Check Passed

No quality issues found – changes LGTM.


Powered by Visor from Probelabs

Last updated: 2025-12-19T15:02:30.825Z | Triggered by: pr_updated | Commit: 7ba0e58

💡 TIP: You can chat with Visor using /visor ask <your question>

@kolavcic kolavcic self-requested a review December 19, 2025 15:00
Copy link
Contributor

@kolavcic kolavcic left a comment

Choose a reason for hiding this comment

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

lgtm

… v1.16.0 in values.yaml files across all components.
@github-actions
Copy link

🚨 Jira Linter Failed

Commit: 7ba0e58
Failed at: 2025-12-19 15:01:56 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details
failed to validate branch and PR title rules: branch name 'release-5.0.0' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

  • Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
  • Verify your PR title matches the branch's Jira ticket ID
  • Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.

@ilijabojanovic ilijabojanovic merged commit 51f0850 into main Dec 19, 2025
7 of 15 checks passed
@ilijabojanovic ilijabojanovic deleted the release-5.0.0 branch December 19, 2025 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants