feat(sdk): regenerate vendored SDK to the 1.6.0 API surface (#150)

.github/workflows/ci.yml

@@ -173,7 +173,7 @@ jobs:
             -e JWT_SECRET="${JWT_SECRET}" \
             -e RATE_LIMIT_ENABLED="false" \
             -p 8081:8080 \
-            ghcr.io/artifact-keeper/artifact-keeper-backend:1.4.0
+            ghcr.io/artifact-keeper/artifact-keeper-backend:1.6.0
       - name: Wait for backend
         run: |
           for i in $(seq 1 60); do

CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.6.0] - 2026-07-19
+
+Foundation for the 1.6.0 line (epic #149): the bundled SDK is regenerated against
+the Artifact Keeper **v1.6.0** OpenAPI surface. Feature commands that build on the
+new API operations land in follow-up releases.
+
+### Changed
+
+- Regenerated the vendored SDK from the OpenAPI **v1.6.0** spec via `cargo xtask generate` (#150); SDK version tracks the API at `1.6.0`. Adds the new `projects` operation surface and 1.6.0 request fields (repository APT/npm/Debian/versioning/project options, SAML group mapping)
+- Dropped the #98 spec-fidelity workarounds now that the v1.6.0 spec is correct: `ak service-account create`, `ak email-subscriptions subscribe`, and `ak lifecycle update` call the strict generated SDK methods instead of raw HTTP (endpoints now declare `201`/`UpdateLifecyclePolicyRequest` as appropriate)
+
 ## [1.2.0] - 2026-07-13
 
 ### Added

Cargo.toml

@@ -3,7 +3,7 @@ members = ["sdk", "xtask"]
 
 [package]
 name = "artifact-keeper-cli"
-version = "1.2.0"
+version = "1.6.0"
 edition = "2024"
 description = "CLI/TUI tool for Artifact Keeper — an enterprise artifact registry"
 license = "MIT"

sdk/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "artifact-keeper-sdk"
-version = "1.4.0"
+version = "1.6.0"
 edition = "2024"
 description = "Generated Rust SDK for the Artifact Keeper API"
 license = "Apache-2.0"