Low priority backlog item.
Problem
Some skills in downstream repositories depend on TypeSpec behavior and can fail validation when TypeSpec package versions are updated. We need a path that lets those skills remain independently updatable instead of requiring every TypeSpec release update to include fixes for all downstream skills.
Context
During release-process follow-up discussion, the data-plane linter-rule coverage guidance in azure-rest-api-specs was called out as an example:
https://github.com/Azure/azure-rest-api-specs/blob/main/.github/skills/azure-api-review/references/data-plane-linter-rule-coverage.md#-landing----merged-upstream-not-yet-running-here
Desired outcome
Investigate how to make skills that rely on TypeSpec robust to TypeSpec package updates and allow skill owners a short update window after a TypeSpec library version update.
Low priority backlog item.
Problem
Some skills in downstream repositories depend on TypeSpec behavior and can fail validation when TypeSpec package versions are updated. We need a path that lets those skills remain independently updatable instead of requiring every TypeSpec release update to include fixes for all downstream skills.
Context
During release-process follow-up discussion, the data-plane linter-rule coverage guidance in azure-rest-api-specs was called out as an example:
https://github.com/Azure/azure-rest-api-specs/blob/main/.github/skills/azure-api-review/references/data-plane-linter-rule-coverage.md#-landing----merged-upstream-not-yet-running-here
Desired outcome
Investigate how to make skills that rely on TypeSpec robust to TypeSpec package updates and allow skill owners a short update window after a TypeSpec library version update.