Closed czechboy0 closed 1 month ago
Should we instead keep it but relax the rule. Be good to know when we're breaking the underscored library product?
We don't even attempt to keep the underscored library's API stable, it's purely for experimentation with in-memory codegen. So I don't particularly care when we break its API.
Motivation
This package doesn't have any library products that would need to maintain API stability, so we don't need to run the CI.
We only have
_OpenAPIGeneratorCore
, which is underscored and not expected to be API stable (so it can only be used using anexact: "..."
constraint). But we don't want to fail CI when we change that API (right now it's introducing noise in: https://github.com/apple/swift-openapi-generator/pull/627)Modifications
Disable API breakage check.
Result
Disabled that CI step.
Test Plan
N/A