Skip to content

[TES-5250] Mark tes-operator 1.3.0 and 1.5.0 as deprecated#95

Open
ashutosh-tenable wants to merge 2 commits into
mainfrom
TES-5250-deprecate-tes-operator-1.3.0
Open

[TES-5250] Mark tes-operator 1.3.0 and 1.5.0 as deprecated#95
ashutosh-tenable wants to merge 2 commits into
mainfrom
TES-5250-deprecate-tes-operator-1.3.0

Conversation

@ashutosh-tenable

Copy link
Copy Markdown
Contributor

Summary

  • Marks tes-operator chart versions 1.3.0 and 1.5.0 as deprecated in the helm repository index, per the TES 18-month version lifecycle policy.

Changes

  • index.yaml: Added deprecated: true to tes-operator 1.3.0 (GA 2025-01-13, deprecated since 2026-01-31)
  • index.yaml: Added deprecated: true to tes-operator 1.5.0 (GA 2025-05-29, deprecated since 2026-05-31)

Background

Both versions are in the 12-18 month deprecated window per the TES version lifecycle policy. Helm will print a deprecation warning on install but will not block existing customers from using these versions.

Policy: https://tenable.atlassian.net/wiki/spaces/TES/pages/3468853255
Ticket: TES-5250

Breaking Changes

None — existing installations are unaffected.

Test Plan

  • Run helm repo update tenable && helm search repo tenable/tes-operator --versions and verify 1.3.0 and 1.5.0 show as deprecated

Ashutosh Saxena and others added 2 commits June 24, 2026 21:55
Adds deprecated: true to the tes-operator 1.3.0 entry in index.yaml.
Version 1.3.0 (GA 2025-01-13) is now 12-18 months old, placing it in
the Deprecated tier per the TES version lifecycle policy.

Helm will print a deprecation warning on install but will not block
existing customers from using this version.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Version 1.5.0 (GA 2025-05-29) is 13 months old and in the deprecated
window per TES version lifecycle policy.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@ashutosh-tenable ashutosh-tenable requested review from a team as code owners June 24, 2026 22:14
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.

1 participant