Repository navigation
chore(rustcfml): bump engine pin to v0.738.1 - #4614
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Peter Amiri <peter@alurium.com>
This was referenced Oct 20, 2026
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.
Automated RustCFML engine bump (daily version check).
Pinned
v0.732.0→v0.738.1.The full core suite ran green against the new engine, so this PR
bumps
tools/rustcfml/ENGINE_VERSIONand the per-asset sha256 pins intools/rustcfml/ENGINE_SHA256(from the release's published digests),plus the CLI's copies of both in
cli/lucli/services/rustcfml/RustCFMLEngine.cfc, and regeneratestools/rustcfml/baseline.jsonto the new engine's result set.If the suite had shown new failures, the pin would have been left
unchanged and this PR would not exist.