fix(release): Enforce quality gates and organize Rust modules - #229
Merged
Merged
Conversation
Resolve RUSTSEC-2026-0285 discovered by the release quality gate.\n\nRefs #224
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.
Summary
Release publication previously ran independently of quality checks, Console checks did not enforce TypeScript types, and embedded assets could remain stale across builds. This change makes publication depend on the reusable Quality workflow for the same commit and completes the corresponding validation paths.
just releaseentrypoint with incremental asset regressions.Validation
just quality: passed, including 702 Rust fast tests, 239 Console tests, formatting, lint/type checks, builds, embedded asset regressions and release metadata tests.vp exec tsc --noEmit: passed. Temporary incompatible assignments confirmed that both TypeScript checkers reject type errors; the probes were removed.cargo msrv find: established Rust 1.88; finaljust msrvpassed after the Rust changes and dependency update.just release: passed. Both binaries report version 0.1.0; the Control API binary contains the current Console HTML and all 121 JavaScript assets.actionlint,cargo auditandvp pm audit: passed. Docker Bake dry runs confirm that verification and publication use identical targets, tags and build inputs. Temporary shell checks cover multi-tag selection, all six binary checks, early failure and empty-tag rejection.Earlier packaging validation: Quality run 34957058990 passed all six jobs for commit
0d478fd2ceb2b1e14c514dc158c35610b4640436: Quality, Linux/macOS MSRV, 31 Control API service regressions plus three Redis cache regressions, Node delivery smoke, and Debian/Slim/Alpine image builds with packaged binary checks. Image verification now runs in Release; PR Quality has five jobs.Final PR Quality run 34969634955 passed all five jobs for commit
1414ca0f37fc470cb0349e65df58fa0659bbf92f: Quality, Node delivery smoke, Linux/macOS MSRV, and PostgreSQL/Redis regressions. The run was triggered only bypull_requestand contains no distributable-image build job.Tracking
Parent tracking issue: #219. Milestone: 0.1.0.
Closes #220
Closes #221
Closes #222
Closes #223
Closes #224
Closes #225
Closes #226
Closes #227
Closes #228
Known Limitations