Skip to content

fix(runtime): target SolverForge 0.26.1 - #9

Merged
blackopsrepl merged 2 commits into
mainfrom
fix/target-solverforge-0.26.1
Nov 11, 2026
Merged

blackopsrepl merged 2 commits into
mainfrom
fix/target-solverforge-0.26.1

Conversation

@blackopsrepl

Copy link
Copy Markdown
Contributor

Closes #8. Gates on this tree against published 0.26.1: make ci-local EXIT 0 (294 passed, 0 failed); make pre-release EXIT 0 for all eight apps.

The README now says the app preserves the scheduling concepts of the original Java application.
SolverForge 0.26.1 keeps late acceptance's score history unless a hard or
medium level changes, so the five apps that search with late acceptance
accept the worsening moves the algorithm is meant to accept again, and its
scalar ruin/recreate draws batches without an entity-sized permutation.
Every app requests and locks the 0.26.1 crates, and its app metadata,
README and WIREFRAME name the new runtime target.

Closes #8
@blackopsrepl
blackopsrepl merged commit e88bc0e into main Nov 11, 2026
2 checks passed
@blackopsrepl
blackopsrepl deleted the fix/target-solverforge-0.26.1 branch November 11, 2026 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(runtime): target SolverForge 0.26.1

1 participant