Conversation
This branch has not been deployed
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.
What: Start #93 alongside uibcdf/molsysmt#237 without changing the current 3.11-3.13 release candidates. This draft widens candidate metadata and adds a Linux/macOS Python 3.14 source-pair workflow pinned to MolSysMT commit 3485f8ddf0924f307dd8a089dea4ed8b51276600.\n\nHow: The new workflow builds both sources, checks the installed Rust extension and viewer resources, and runs the Viewer Python suite. Existing package CI is intentionally skipped by this draft title; the new source-pair job still runs. Local Linux 3.14 evidence: 19 integration tests, 15 distribution tests, and 2,069/2,090 full-suite tests passed initially; the five failures were traced to omitted Jinja2/MDTraj and a stale generated capability audit, and all three affected files passed 208 tests after correction.\n\nWhy draft: This is not a resolver-consistent release gate. The MolSysMT checkout still has a 0.21.x development identity below Viewer\u0027s >=0.22.0 floor, staging remains scoped to 3.11-3.13, and the optional UIBCDF Qt stack does not resolve on 3.14. Do not merge or claim public 3.14 support until the coordinated package pair and suite-policy gates pass.