types-update

Types Update Skill

Updates @forklift-ui/types from upstream sources (Forklift, Kubernetes, KubeVirt, CDI), publishes a new version, and bumps the consumer project.

For conflict resolution rules, Jira payload template, CRD verification, and edge cases see reference.md.

Prerequisites

• gh CLI authenticated with access to kubev2v/forklift-console-types
• User's fork of kubev2v/forklift-console-types cloned locally (or clonable)
• ~/.jira-creds configured (see ~/.cursor/rules/jira-api.mdc)
• curl, jq, npm, node >= 20 installed
• Java runtime (required by openapi-generator-cli in the types repo)
• Types package depends on @openshift/api-types (installed via npm ci in the types repo). After every generation update, run npm run align:k8s-base (see Phase 3e / MTV-6057).

Permissions — Cross-Project File Access

The types repo (forklift-console-types) lives outside the current workspace. The Cursor sandbox blocks writes to paths outside the workspace, which causes repeated permission prompts.

Rules for all phases that touch the types repo (Phases 2.5, 3, 4):

1. Always use required_permissions: ["all"] on every Shell call whose working_directory is the types repo.
2. Use Shell for file edits in the types repo — do NOT use the Write or StrReplace tools for files outside the workspace. Instead write files via shell (e.g. cat <<'CONTENT' > path/to/file.ts ... CONTENT). This avoids per-file permission prompts.
3. Batch operations — combine multiple related edits into a single Shell call when possible to minimise approval prompts.
4. Phases that only run in the consumer project (this workspace) do not need special permissions.

---

Workflow

Copy this checklist and track progress:

Types Update Progress:
- [ ] Phase 1: Setup and discovery
- [ ] Phase 2: Create Jira ticket
- [ ] Phase 2.5: Update inventory types from Go source
- [ ] Phase 3: Update generated types in forked repo
- [ ] Phase 3e: Run `npm run align:k8s-base` (mandatory after generation)
- [ ] GATE 1: User approves conflict resolution (if any)
- [ ] Phase 4: Version bump, tracking update, and PR
- [ ] GATE 2: User confirms types PR is merged
- [ ] Phase 5: Create GitHub release and wait for npm publish
- [ ] Phase 6: Update consumer project (forklift-console-plugin)
- [ ] Phase 7: Monitor CI on consumer PR