Repository navigation
ci: qualify the Node 22.23.4 security runtime - #12
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.
Description
Pin both deployment qualification jobs to Node 22.23.4. The previous Node 22 selector reused cached 22.23.3, so a green run did not test the security runtime staged for Sluthub. Application source, dependencies and runtime configuration are unchanged.
AI Disclosure: Codex authored these two workflow version changes and ran the validation under the owner's maintenance authorization for this maintained fork.
How Has This Been Tested?
Both canonical jobs passed at 49112de in run 39730334355, including lint, formatting, types, tests, the production build and auxiliary tool checks. Both setup logs explicitly report Node v22.23.4. The previous passing run on cached v22.23.3 is retained separately.
The staged official Linux runtime also passes a service-account version check, the existing Requests Manager SQLite in-memory and bcrypt smoke checks, and entry-point syntax validation. Production activation remains a separate guarded operation.
Screenshots / Logs (if applicable)
Canonical Node 22.23.4 checks
Checklist: