Chore: point the engine pin at the current CLI main - #65
Merged
Conversation
The pin sat on 5aea416, the branch tip that PR #94 merged, rather than on fe8eb6d, the merge commit that is now the CLI's main. The two trees are byte-for-byte identical, so nothing about the engine changes here — this only stops the submodule showing as modified against a commit that is no longer where main points.
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
1 participant
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
Bookkeeping only. Desktop's pin to the MandoCode engine pointed at a commit that is no longer where the engine's main branch sits. This moves the pin onto the current main. The engine code Desktop builds against does not change at all.
Why this matters
The engine is brought into Desktop as a pinned commit, so it is always clear which engine build a given Desktop build shipped with. That pin was left on the tip of a feature branch rather than on the merge commit that landed it. The result was cosmetic but confusing: a fresh checkout showed the engine as "modified" against main even with nothing changed locally, which makes it harder to tell a real engine change from noise.
What changed
Scope and risk
Low. One pointer, no code. Desktop compiles against exactly the same engine source before and after.
No changelog entry: there is no user-visible change to record.
Verification
Verified the two engine commits have identical contents (an empty diff between them). Desktop builds clean and all 330 Desktop tests pass on this engine.