github-actions[bot] opened a new pull request, #254:
URL: https://github.com/apache/fineract-backoffice-ui/pull/254

   <!-- fineract-spec-sync -->
   Apache Fineract's OpenAPI spec has changed. This regenerates `src/app/api/` 
from it.
   
   | | |
   |---|---|
   | Spec version | `1.16.0-SNAPSHOT` |
   | Upstream commit | _unknown_ |
   | Image | 
`apache/fineract@sha256:5bd93151fa0d6645d00b75dec2ab6c67a01e6279880524daa841d20a5f633433`
 |
   | Paths / operations / schemas | 602 / 967 / 1472 |
   | Run | 
https://github.com/apache/fineract-backoffice-ui/actions/runs/31198660181 |
   
   ### Compile check
   
   ✅ `npm run build` passed — no call site was broken by this change.
   
   ### API surface diff
   
   | | added | removed | changed |
   |---|---|---|---|
   | paths | +2 | | |
   | operations | 2 | 0 | 5 |
   | schemas | 5 | 0 | |
   
   No operations were removed, so no existing call site can break.
   
   <details><summary>Added operations</summary>
   
   ```
   PUT /v1/working-capital-loans/external-id/{loanExternalId}/mark-as-fraud
   PUT /v1/working-capital-loans/{loanId}/mark-as-fraud
   ```
   </details>
   
   
   
   ---
   
   Provenance for this spec is recorded in 
`public/api/fineract.provenance.json`.
   See [`DOCS/OPENAPI_GENERATOR.md`](DOCS/OPENAPI_GENERATOR.md) and
   
[`DOCS/adr/0002-automated-fineract-spec-sync.md`](DOCS/adr/0002-automated-fineract-spec-sync.md).
   
   > **CI may not have run on this PR.** Without a `SPEC_SYNC_TOKEN` secret it 
is opened
   > with the default `GITHUB_TOKEN`, which cannot trigger workflows — so 
`api-client-drift`,
   > `build` and the rest stay silent. Close and reopen the PR (or push an 
empty commit) to
   > run them. The compile check above is a preview, not a substitute.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to