Data Product Changelog Generator
Outcome
compare two product manifests and generate a deterministic semantic changelog with breaking-change flags
Problem solved
- Compare two product manifests and generate a deterministic semantic changelog with breaking-change flags.
Who it is for
dataset publishers, API maintainers, and release engineers
Exact contents
- LICENSE.md
- README.md
- REFUND.md
- SUPPORT.md
- cover.svg
- developer/IMPLEMENTATION-GUIDE.md
- developer/README.md
- developer/input-schema.json
- developer/openapi.json
- developer/output-schema.json
- developer/package.json
- developer/sample-input.json
- developer/sample-output.json
- developer/server.mjs
- developer/smoke-test.json
- developer/test.mjs
- developer/tool-profile.json
- download-manifest.json
- gumroad-product.json
Inputs and outputs
Inputs
- Provide a JSON object with at least 1 property/properties that follows developer/input-schema.json.
- Start with developer/sample-input.json; it is a deterministic example, not buyer data.
Outputs
- The local runtime returns a JSON result with: status, operation, product_slug, result, warnings, external_calls_attempted.
- developer/sample-output.json is the deterministic output example.
Formats
- JSON
- OpenAPI
- Markdown
- Node.js ES modules
How it works
- Install Node.js >=20.
- No third-party runtime package is required.
- Run npm test in the developer directory.
- Run node developer/cli.mjs --input developer/sample-input.json.
Compatibility and requirements
- Runtime: node_20_or_newer (package requirement >=20).
- Buyer-operated local HTTP API defaults to 127.0.0.1:8787.
- The bundled default runtime makes no network call and includes no credentials.
Real sample or preview
- developer/sample-input.json and developer/sample-output.json are included as deterministic fixtures.
- developer/test.mjs is included for the offline reproducible smoke test.
Source provenance and freshness
- Data Product Changelog Generator source requirements — Zentra-owned public catalog metadata used for deterministic product, package, source-attribution, and service workflow evidence. — Official/public reference URL selected from Zentra curated source URL catalog. Concrete live extraction remains gated by robots, terms, credentials, and route-specific source-policy checks.
- Zentra prepared product artifact — Prepared from Zentra-owned product metadata until a route-specific source connector is configured. — Zentra-owned product metadata generated inside the application until an approved route-specific public source is attached.
release_driven
Version and last verification
Version 1.0.0
Last verified 2026-08-13T08:16:49+02:00
License and permitted use
Use is limited to the rights expressly stated in LICENSE.md in the immutable downloaded archive; this listing grants no additional rights.
Update policy
This is an immutable, versioned fixed download. The archive does not state an automatic update entitlement.
Limitations
- No credentials, paywalled bypass, private data, raw private run IDs, or unsafe source scraping is included in this route-native product record.
- No third-party redistribution restriction detected for prepared metadata-only artifacts.
- No hosted Zentra API, managed service, third-party account, credential, or done-for-you deployment is included.
- Authentication, TLS, deployment, optional third-party connections, source rights, and security review remain the buyer’s responsibility.
- Review source terms, licences, privacy, and consequential decisions with qualified owners before production use.
Product-specific FAQ
- Does this include a hosted Zentra API?
- No. The delivered product is a self-hosted developer kit.
- Does the default runtime require credentials or make network calls?
- No. The archive declares no included credentials and no default network calls.
Related products and bundle path
- No related product or bundle entitlement is asserted by the immutable archive.
Support boundary
This is a self-hosted developer kit, not a hosted Zentra API or managed service. The local API defaults to 127.0.0.1:8787; buyers own authentication, TLS, deployment, optional third-party connections, source rights, security review, and final decisions.