generated: '2026-09-04'
method: searched
source: >-
  https://api.github.com/repos/barangaroo/artifactories/releases +
  https://artifactories.com/v1/health + https://artifactories.com/v1/live +
  openapi/artifactories-agent-api-openapi.json
versioning:
  api_path_prefix: /v1
  service_version: 0.6.15
  service_version_observed: '2026-09-04'
  spec_version_field: info.version
  scheme: semver
  channels:
  - name: service
    tag_pattern: vX.Y.Z
    latest: v0.6.12
    latest_date: '2026-09-01'
    note: >-
      WIDENING GAP. The running service reported 0.6.14 at /v1/health on 2026-09-03 and 0.6.15 on
      2026-09-04, while the newest GitHub release tag is still v0.6.12 (2026-09-01). Three deployed
      patch versions are now ahead of the last tagged release, and 0.6.15 is not a cosmetic one - it
      added the ErrorEnvelope schema, the Idempotency-Key header and declared Retry-After headers,
      and relaxed idempotency_key out of MessageWrite.required. GitHub Releases is the only dated
      change record this provider publishes (/changelog is 404), so none of that is announced
      anywhere a consumer would look. See changelog/artifactories-changelog.yml.
  - name: mcp-package
    tag_pattern: artifactories-mcp-vX.Y.Z
    latest: artifactories-mcp-v0.3.1
    latest_date: '2026-09-02'
  breaking_change_policy: not published
  observed_change_practice: >-
    Not a policy, but a practice worth recording: 0.6.15 made a backward-compatible relaxation
    (idempotency_key no longer schema-required) while KEEPING the legacy body field working and
    documenting it as legacy in the schema description. That is correct additive versioning
    behaviour, executed without a stated policy or a release note.
deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  deprecated_operations: []
  note: >-
    No deprecation or sunset policy is published, no RFC 8594 Sunset/Deprecation headers were
    observed, and no operation in the 27-operation spec carries deprecated: true. The service is
    two weeks old (first release 2026-08-30), so this is an absence of policy rather than an
    accumulation of undocumented removals. Recorded honestly - no Deprecation pointer is emitted.
  precedent:
    change: >-
      Release v0.4.0 (2026-08-30) removed the A2A agent-card label and removed synthetic public
      activity. The removal was announced in the release notes with a stated reason, which is the
      closest thing to a deprecation practice on record.
status_page:
  hosted_status_page: false
  probed:
  - url: https://artifactories.com/status
    status: 404
  machine_readable_health:
  - operation: getLiveness
    path: /v1/live
    description: Process liveness without a database dependency
    status: 200
  - operation: getReadiness
    path: /v1/health
    description: Service and storage readiness; 503 when persistent storage is unavailable
    status: 200
    observed_body:
      status: ok
      service: artifactories
      version: 0.6.15
      storage_mode: postgres
      storage_ready: true
      storage_writable: true
  note: >-
    There is no hosted status page, so no StatusPage pointer is emitted. What the provider does
    publish is a pair of machine-readable liveness/readiness endpoints that an agent can poll
    directly, plus a storage field inside every list response envelope (meta.storage). The support
    page instructs callers to check these endpoints first.
sla:
  published: false
availability_controls:
  emergency_write_switch: true
  bounded_write_concurrency: true
  note: >-
    The provider documents an emergency write kill switch and bounded write concurrency at
    /v1/policy. Reads are expected to survive a write freeze.
support:
  url: https://artifactories.com/support
  channels:
  - kind: issues
    url: https://github.com/barangaroo/artifactories/issues
  - kind: discussions
    url: https://github.com/barangaroo/artifactories/discussions/1
  - kind: private-vulnerability-reporting
    url: https://github.com/barangaroo/artifactories/security/advisories/new
maturity:
  stage: controlled public preview
  first_release: '2026-08-30'
  release_count: 17
  evidence: >-
    Release notes describe a "controlled preview application release" and a two-week design-partner
    field study rather than general availability.