Justin fde668ddb6 fix(release): register runpod-migrate with release-please ...

The skill added in #46 was never listed in release-please-config.json
extra-files, so release-please bumped every other version-bearing file to
1.2.0 and left it at 1.1.2. That fails the version guard on release PR #47
and would fail on every release after it.

check_versions.py globs skills but release-please enumerates them, so a new
skill silently breaks the *next* release rather than the PR that adds it.
The guard now also asserts every skill it globs is registered, naming the
missing paths — the failure lands on the PR that can cheaply fix it.

2026-08-19 12:47:53 -04:00

..

check_links.py

fix(skills): address content/structure review findings

2026-07-08 13:49:52 -04:00

check_migrate_class3.py

feat(runpod-migrate): GraphQL / REST v1 → REST v2 migration skill (#46)

2026-08-19 12:31:18 -04:00

check_migrate_scanner.py

feat(runpod-migrate): GraphQL / REST v1 → REST v2 migration skill (#46)

2026-08-19 12:31:18 -04:00

check_migrate_tables.py

feat(runpod-migrate): GraphQL / REST v1 → REST v2 migration skill (#46)

2026-08-19 12:31:18 -04:00

check_runpod_branding.py

docs(golden-paths): add 09 custom-serverless dual-mode dev loop (spec) + fix CI

2026-07-10 17:07:37 -04:00

check_versions.py

fix(release): register runpod-migrate with release-please

2026-08-19 12:47:53 -04:00

validate_marketplace.py

fix(marketplace): use CC-compatible explicit source path

2026-07-13 14:36:23 -04:00