Repository navigation
Fix CI references and gate releases on verified artifacts - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR: Fix invalid core-reference expressions in CI, validate workflows before building, and publish the exact release ZIP that passed the database tests and installer checks.
The CI matrix no longer defines
core_ref, but two checkout steps still referenced it. Both now use the selected Inventoros ref directly. A checksum-pinned actionlint job catches workflow and shell errors before UI builds; this also corrects two unquoted GitHub output paths. Jobs use Ubuntu 24.04 with explicit timeouts, read-only permissions and seven-day CI artifact retention.Release tags call the same CI workflow, including the three-database test matrix and real ZIP lifecycle verification. Publishing downloads that verified artifact and checks its SHA-256 instead of rebuilding a second archive. Only the publishing job has write permission. Tag/changelog validation, exact version-specific release notes and existing-tag verification precede publishing.
Validation:
The repository is now public. Hosted CI on main passes every job: workflow validation, UI bundle, SQLite/PostgreSQL/MySQL tests and ZIP installation verification.