generated: '2026-09-12'
method: searched
source: https://developer.harness.io/release-notes/platform.md, https://developer.harness.io/release-notes/, https://status.harness.io,
  https://apidocs.harness.io/#section/Introduction/Versioning-Beta, plus deprecated:true operations derived from
  openapi/_original/harness-apis-openapi.yaml
provider: Harness
providerId: harness
versioning:
  scheme: generation-in-path
  current: v1
  docs: https://apidocs.harness.io/#section/Introduction/Versioning-Beta
  description: The API Generation is carried in the path (app.harness.io/v1/...). Harness states the Generation
    changes only on a system-wide refactoring of core concepts. A date-header version for Beta APIs is announced
    as planned but the version number "is yet to be announced". In practice, change is absorbed by operation-level
    V2/V3 suffixes with the predecessor flagged deprecated.
  date_header_version: announced, not yet published
deprecation_policy:
  published: true
  url: https://developer.harness.io/release-notes/platform
  mechanism: A "Deprecation notice" section in the Platform release notes names removed endpoints; the OpenAPI marks
    superseded operations deprecated:true.
  rfc8594_sunset_header: false
  rfc8594_note: No Sunset or Deprecation response header is declared anywhere in the 2,883-operation contract. Deprecation
    is communicated in prose release notes and as a spec flag only — an agent cannot learn of a retirement at runtime.
  retired_endpoints:
  - '[GET|PUT|POST|DELETE] api/resourcegroup/{identifier}'
  - POST api/resourcegroup/filter
  - GET api/resourcegroup
  retired_source: https://developer.harness.io/release-notes/platform (Deprecation notice)
  breaking_change_notices:
  - title: Audit Trail YAML optimization
    effective: '2026-08-16'
    impact: Audit entries no longer store old/new YAML snapshots when nothing meaningfully changed. Automation reading
      YAML out of audit entries must handle its absence.
  - title: Bitbucket Cloud cross-workspace API deprecation
    effective: Delegate v26.02.88600 / SCM Service v1.45.1
    impact: Repository-level access tokens can no longer Test Connection or list repositories; workspace-level tokens
      required.
deprecated_operations:
  count: 21
  source: openapi/_original/harness-apis-openapi.yaml
  operations:
  - operationId: getConnectorList
    path: /ng/api/connectors
    method: GET
    tags:
    - Connectors
    summary: List all Connectors using filters
  # ... other operations omitted for brevity ...
release_cadence:
  scheme: monthly minor, 1.163.x as of September 2026
  notes_url: https://developer.harness.io/release-notes/
  per_module: true
  modules_with_own_notes:
  - Platform
  - Delegate
  - Code Repository
  - Self-Managed Enterprise Edition
  - Artifact Registry
  - Chaos Engineering
  - Cloud Cost Management
  - Continuous Delivery and GitOps
  - Continuous Integration
  - Continuous Error Tracking
  - Database DevOps
  - Feature Flags
  - Feature Management & Experimentation
  - AI Test Automation
  - WAAP
  - Harness Solutions Factory
progressive_deployment: Harness deploys to SaaS clusters progressively — a feature in the notes may not yet be
  live on a given account cluster.
status_page:
  url: https://status.harness.io
  platform: Atlassian Statuspage
  machine_readable: https://status.harness.io/api/v2/summary.json
  probe:
    url: https://status.harness.io/api/v2/summary.json
    status: 200
    checked: '2026-09-12'
  in_product: Harness also ships an account-scoped Status Portal showing the health of the specific cluster and
    enabled modules (https://developer.harness.io/harness-platform/use-harness-platform/status-portal).
sla:
  published: false
  note: No public uptime SLA document was found.
security_advisories:
  published_behind_request: true
  note: Harness publishes a security adv
# ... rest omitted ...

deprecation:
  method: none
  note: No deprecation field originally present.