Artifacts [release]
When creating a new release (and corresponding Git tag), a tar.gz archive is generated and attached to that release. This archive contains all the key files required to represent the platform at that specific version, including:
platform-descriptor.json
A folder with application descriptors
package.json and yarn.lock (for dependency management)
stripes.config.js and stripes.modules.js
By packaging these files together, the release artifact fully captures the state of the platform‑lsp repository at the time of tagging, making it easy to share and deploy consistently.
Platform descriptor (example)
This platform-descriptor.json defines a FOLIO/Eureka “platform” by listing its essential metadata (name, description, version) along with all modules and services it requires. Under eureka-components, you see core infrastructure modules (e.g. Keycloak, Kong, manager, sidecar) with their versions. The applications section breaks down required vs. optional apps, and also declares key dependencies like PostgreSQL, Kafka or OpenSearch. Together, this descriptor provides a single source of truth for deploying or assembling the platform, ensuring each component is correctly versioned and included in the final environment.