Description

This pull request updates the PR validation workflow to enforce labeling for PaaS compatibility. Now, PRs must be tagged with either No-PaaS-breaking-change or PaaS-breaking-change to clarify their impact on PaaS compatibility.

PR validation workflow improvements:

• Updated .github/workflows/validate-prs.yml to require PRs to include either the No-PaaS-breaking-change or PaaS-breaking-change label, ensuring that PaaS compatibility is explicitly indicated.

Related issues

Addresses AB#178281.

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)