Repository navigation
Extend supported versions to R2022a, R2025a, R2026a - #47
Merged
Merged
Conversation
Widens the GmatVersion type to {R2022a, R2025a, R2026a} and extends
MIN_SIZE_BYTES with conservative floors based on real installer sizes
verified by HEAD against SourceForge:
R2022a: 372 MiB observed → 360 MiB floor
R2025a: 402 MiB observed → 390 MiB floor
R2026a: 383 MiB observed → 380 MiB floor (unchanged)
NASA never released R2023a or R2024a — no SourceForge artifacts exist
for those years. Refs #36.
R2026a renamed Ex_R2014a_HighFidelitySRP.script to Ex_HighFidelitySRP.script. The smoke check now resolves the right filename per version: R2022a and R2025a fall back to the older name, R2026a uses the new one. Both variants were verified headless-safe (no OrbitView/OpenFrames/XYPlot resources). Refs #36.
Remove outright 'R2026a is the only supported version' claims that v0.1
left behind in user-facing prose. The version-matrix tables in README
and inputs/outputs.md, the roadmap table, the Python-ABI guidance, and
yaml/error-message examples are explicitly out of scope and untouched
here — those belong to the v0.2 docs issue.
Also update two factual claims that the per-version smoke sample
mapping invalidates:
- inputs-outputs.md / getting-started.md / troubleshooting.md no
longer name the smoke sample by filename (it varies per release).
- run-mission-script.md notes the R2026a rename of
Ex_R2014a_HighFidelitySRP.script.
Refs #36.
Regenerated bundle after the R2022a/R2025a/smoke-sample changes.
Prettier widened the column to match the longest row after the samples/ description was rewritten.
The supported-versions expansion ships post-v0.1, so the previous wording that anchored 'v0.1' as the release that supports R2022a/R2025a/R2026a was technically wrong. Rewrite the affected paragraphs in present tense and bump 'scoped for v0.2' to 'tracked under a future milestone' since the version-matrix landing in v0.2 displaces the prior Windows/macOS v0.2 commitment.
djankov
marked this pull request as ready for review
April 30, 2026 23:08
djankov
added a commit
that referenced
this pull request
May 1, 2026
- Populate CHANGELOG.md with the [0.2.0] - 2026-05-01 section, aggregated from the 11 merged v0.2 PRs (#47, #48, #49, #50, #51, #52, #53, #55, #56, #57, #58). - Bump package.json version from 0.1.0 to 0.2.0. The v0.2 row in the README roadmap was already trimmed-and-relabelled (`v0.2 _(current)_`) by #58 ahead of the cut, mirroring the v0.1 cut precedent (#35), so no README change is needed here. Closes #46.
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.
Summary
GmatVersionto{R2022a, R2025a, R2026a}; add a per-versionMIN_SIZE_BYTESmap with conservative floors verified by HEAD against SourceForge (R2022a 360 MiB, R2025a 390 MiB, R2026a 380 MiB unchanged).samples/Ex_R2014a_HighFidelitySRP.script; R2026a usessamples/Ex_HighFidelitySRP.script(renamed upstream). Both variants verified headless-safe (no OrbitView / OpenFrames / XYPlot resources).docs/, andaction.yml. The version-matrix tables, the roadmap, the Python-ABI guidance, and yaml/error-message examples are explicitly out of scope and untouched — those go with the v0.2-surface docs issue.dist/.extract.tsneeded no change — it was already version-parameterized viapath.join(stagingDir, 'GMAT', version), and theGMAT/<version>/api/BuildApiStartupFile.pywrapper layout was confirmed identical across all three tarballs.NASA never released R2023a or R2024a — there are no SourceForge artifacts, so
SUPPORTED_VERSIONSskips those years.Test plan
npm run all(format:check + lint + typecheck + build) green locally.api/BuildApiStartupFile.pypaths verified bytar tzfagainst freshly-downloaded SourceForge tarballs.~/gmat-R2026a/.Ubuntu × R2026aself-test job.Out of scope (per issue)
docs/inputs-outputs.md(handled by the v0.2-surface docs issue).CHANGELOG.md(release-cut only).Closes #36