...
This flowchart illustrates how version increments propagate through different levels of the FOLIO/Eureka ecosystem—from individual modules (UI or back-end) up to the encompassing application and platform. Each decision (patch, minor, or major) at the module level triggers a corresponding version bump at the application and platform layers. This ensures consistency and compatibility across all components, so that any change in underlying modules is accurately reflected in the application’s and, ultimately, the platform’s version.
| Drawio | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Modules flow
...
Applications flow
...
This diagram shows the final step of merging a pull request in the platform-lsp repository. After the PR is reviewed and approved, notifies the team (e.g., via Slack). This confirms the updated platform descriptor as the official release, ensuring all changes are properly recorded and communicated.
| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Pull Request Merge Flow: Once approved, the pull request is merged into the release branch. The workflow notifies the team, confirming the updated platform descriptor as an official release.
| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|