docs(ssh): correct stale selector descriptions in manifest (#485 follow-up) #16

Merged
stack72 merged 1 commit from fix/485-followup-docs into main 2026-05-29 15:05:17 +00:00
Owner

Summary

Follow-up to #15. The 2026.05.29.1 release fixed the selector behavior but left two stale selector descriptions in manifest.yaml that still described the removed bare-CEL form — so the published registry docs contradicted the shipped behavior:

  • ## Highlights: "Three selector forms: "all", an explicit name list, or a bare CEL string evaluated per host"
  • Usage example: --input hosts='"prod" in host.tags'

My docs-drift sweep in #15 updated the manifest's top description and all README sites but missed these two blocks lower in the manifest.

Changes

  • Rewrite the Highlights selector bullet to describe the bare name/tag default, the name:/tag:/cel: prefixes, and the bare-CEL deprecation.
  • Fix the usage example to hosts='tag:prod'.
  • Bump 2026.05.29.12026.05.29.2 (manifest and model version) with a matching upgrades entry, so the corrected version is picked up as current. Docs-only — identity upgradeAttributes, no code, schema, or behavior change.

Verification

  • Full gate (from ssh/): deno check / lint / fmt --check clean, 204 tests pass, deno install --frozen clean.
  • Swept the entire manifest.yaml and README.md — no remaining unprefixed bare-CEL examples or "Three selector forms" phrasing.
  • Live check via local extension source: the source resolves 2026.05.29.2 as current and a fresh instance pins typeVersion: 2026.05.29.2; the 19.1 → 29.1 → 29.2 upgrade chain is intact (identity migrations).

🤖 Generated with Claude Code

## Summary Follow-up to #15. The `2026.05.29.1` release fixed the selector behavior but left two stale selector descriptions in `manifest.yaml` that still described the **removed** bare-CEL form — so the published registry docs contradicted the shipped behavior: - `## Highlights`: *"Three selector forms: `"all"`, an explicit name list, or a bare CEL string evaluated per host"* - Usage example: `--input hosts='"prod" in host.tags'` My docs-drift sweep in #15 updated the manifest's top `description` and all README sites but missed these two blocks lower in the manifest. ## Changes - Rewrite the Highlights selector bullet to describe the bare name/tag default, the `name:`/`tag:`/`cel:` prefixes, and the bare-CEL deprecation. - Fix the usage example to `hosts='tag:prod'`. - Bump `2026.05.29.1` → `2026.05.29.2` (manifest **and** model `version`) with a matching `upgrades` entry, so the corrected version is picked up as current. **Docs-only** — identity `upgradeAttributes`, no code, schema, or behavior change. ## Verification - Full gate (from `ssh/`): `deno check` / `lint` / `fmt --check` clean, **204 tests pass**, `deno install --frozen` clean. - Swept the entire `manifest.yaml` and `README.md` — no remaining unprefixed bare-CEL examples or "Three selector forms" phrasing. - Live check via local extension source: the source resolves `2026.05.29.2` as current and a fresh instance pins `typeVersion: 2026.05.29.2`; the `19.1 → 29.1 → 29.2` upgrade chain is intact (identity migrations). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs(ssh): correct stale selector descriptions in manifest (#485 follow-up)
All checks were successful
CI / ssh - lint (pull_request) Successful in 55s
CI / ssh - check (pull_request) Successful in 58s
CI / cve/dirtyfrag - test (pull_request) Has been skipped
CI / cve/mini-shai-hulud - check (pull_request) Has been skipped
CI / ssh - lockfile up to date (pull_request) Successful in 56s
CI / cve/mini-shai-hulud - fmt (pull_request) Has been skipped
CI / cve/mini-shai-hulud - lint (pull_request) Has been skipped
CI / cve/dirtyfrag - lockfile up to date (pull_request) Has been skipped
CI / cve/mini-shai-hulud - test (pull_request) Has been skipped
CI / cve/mini-shai-hulud - lockfile up to date (pull_request) Has been skipped
CI / model/digitalocean - check (pull_request) Has been skipped
CI / ssh - test (pull_request) Successful in 1m7s
CI / model/hetzner-cloud - check (pull_request) Has been skipped
CI / model/digitalocean - lockfile up to date (pull_request) Has been skipped
CI / aws models - sample check (pull_request) Has been skipped
CI / model/hetzner-cloud - lockfile up to date (pull_request) Has been skipped
CI / Dependency Audit (pull_request) Successful in 4m11s
CI / gcp models - lockfiles up to date (pull_request) Has been skipped
CI / cloudflare models - sample check (pull_request) Has been skipped
CI / aws models - lockfiles up to date (pull_request) Has been skipped
CI / gcp models - sample check (pull_request) Has been skipped
CI / cloudflare models - lockfiles up to date (pull_request) Has been skipped
CI / codegen - check (pull_request) Has been skipped
CI / codegen - lockfile up to date (pull_request) Has been skipped
CI / codegen - fmt (pull_request) Has been skipped
CI / codegen - lint (pull_request) Has been skipped
CI / CI Security Review (pull_request) Has been skipped
CI / Adversarial Code Review (pull_request) Has been skipped
CI / Claude Code Review (pull_request) Successful in 1m56s
CI / Merge Gate (pull_request) Successful in 30s
a63fc0dc03
The 2026.05.29.1 release fixed the selector behavior but the manifest's
`Highlights` and usage example still described the removed bare-CEL form
("Three selector forms ... a bare CEL string evaluated per host"). The
published docs therefore contradicted the shipped behavior.

- Rewrite the Highlights selector bullet to describe bare name/tag,
  name:/tag:/cel: prefixes, and the bare-CEL deprecation.
- Fix the usage example to use `hosts='tag:prod'` instead of bare CEL.
- Bump version to 2026.05.29.2 (manifest + model) with a matching
  `upgrades` entry so the corrected version is picked up as current.
  Docs-only — identity upgradeAttributes, no code or schema change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author
Owner

Code Review

Blocking Issues

None.

Suggestions

  1. ssh.ts: consolidate the two import … from "./_lib/schemas.ts" blocks — the value imports (line 36–48) and the type imports (line 49–55) both pull from the same source file. A single import { ApplyArgsSchema, …, type CopyArgs, … } from "./_lib/schemas.ts" would be marginally cleaner, though this is purely stylistic and doesn't block merge.

Summary: Docs-only version bump from 2026.05.29.12026.05.29.2. Both manifest.yaml and ssh.ts versions are consistent. The new upgrades entry for 2026.05.29.2 correctly uses an identity upgradeAttributes transform and accurately describes the change (no code/schema delta). The manifest's Highlights selector bullet and usage example now accurately reflect the name:/tag:/cel: prefix behavior introduced in 2026.05.29.1, removing the stale bare-CEL description. No any types introduced, named export only (export const model), no default export. No test changes needed for a docs-only bump.

## Code Review ### Blocking Issues None. ### Suggestions 1. **`ssh.ts`: consolidate the two `import … from "./_lib/schemas.ts"` blocks** — the value imports (line 36–48) and the type imports (line 49–55) both pull from the same source file. A single `import { ApplyArgsSchema, …, type CopyArgs, … } from "./_lib/schemas.ts"` would be marginally cleaner, though this is purely stylistic and doesn't block merge. --- **Summary:** Docs-only version bump from `2026.05.29.1` → `2026.05.29.2`. Both `manifest.yaml` and `ssh.ts` versions are consistent. The new `upgrades` entry for `2026.05.29.2` correctly uses an identity `upgradeAttributes` transform and accurately describes the change (no code/schema delta). The manifest's `Highlights` selector bullet and usage example now accurately reflect the `name:`/`tag:`/`cel:` prefix behavior introduced in `2026.05.29.1`, removing the stale bare-CEL description. No `any` types introduced, named export only (`export const model`), no default export. No test changes needed for a docs-only bump.
stack72 deleted branch fix/485-followup-docs 2026-05-29 15:05:17 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
swamp-club/swamp-extensions!16
No description provided.