API definitions are not linked to Operations

[TiberiuGarbea]

Command that triggered the bug

apiops extract and publish

Expected behavior

I am trying apiops_cli for managing a multi team APIM.
I extract a single API and push it to a test APIM.
I configure filter with the respective api and required named values. All other are mentioned with [].
I get the API to the test APIM instance, I get the operations, definitions and the named values.
But I do not get the Definitions referenced to the Operations.

Actual behavior

Definitions are found in the export at schemas/1758020457424/schemaInformation.json and they are also visible in the portal at Definitions Tab but they are not linked to respective API operations.
"responses": {
"200": {
"description": "",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/ScanResponse"
},
Schema ref is missing for all operations.

apiops CLI version

$ apiops --version: 0.4.0-alpha.2

Environment details

command runs in a gitlab pipeline on self hosted gitlab runner image: mcr.microsoft.com/dotnet/sdk:6.0
Nodejs version node-v22.14.0-linux-x64

CI/CD environment

None

Is this bug blocking you?

Yes

[azaslonov]

This has already been corrected on main by commit f253356. The post-import operation reconciliation now leaves schema-bound request/response representations owned by the OpenAPI import, instead of PATCHing those arrays and removing the bindings that APIM created.

I verified the focused publisher suite on current main: all 46 tests pass, including the regression 'should not re-send schema-bound response representations in reconcile PATCH'.

The reported version, 0.4.0-alpha.2, predates this fix, and there is not yet a newer published prerelease. The fix will therefore become available in the next release.

[TiberiuGarbea]

Hi Alexander Zaslonov (@azaslonov) ,thank you for the update. Is there a timeline we can expect the next release to be available as an npm package?