The vendored openapi.json has drifted from the live contract
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 0
- Avg merge
- 3h 59m
- Merged PRs (30d)
- 3
Description
The live OpenDPP contract is now 1.16.0
(https://opendpp-node.eu/openapi.json) and the vendored copies no longer match it:
typescript/openapi.json (1.17.0): STALE
java/openapi.json (1.17.0): STALE
python/openapi.json (1.17.0): STALE
Why this matters: check-version-lock.mjs compares package.json against the vendored
spec, so it stays green while stale — a published SDK can target a contract state that no
longer exists and look identical to a current one. This check is the only thing that sees it.
To resolve: re-copy openapi.json from the live contract into typescript/ and java/,
regenerate both clients, bump each artifact's version to the new contract's major.minor
(the PATCH digit is the SDK's own fix lane), add a CHANGELOG.md entry, then tag
sdk-ts-<semver> / sdk-java-<semver> to publish.
Opened automatically by the drift check. It will comment here on each run while drift lasts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the vendored specs in typescript/openapi.json and java/openapi.json, compare them with the live OpenDPP contract, and inspect check-version-lock.mjs for the version-lock behavior. Regenerate both clients, update their versions and CHANGELOG.md entries, then verify the sdk-ts- and sdk-java- tags needed for publishing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi, python, typescript
- Domain
- api, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100