feat: add devtest installers and launch guidance#232
Merged
code-JDS merged 2 commits intoScience-Discovery:devfrom Apr 9, 2026
Merged
feat: add devtest installers and launch guidance#232code-JDS merged 2 commits intoScience-Discovery:devfrom
code-JDS merged 2 commits intoScience-Discovery:devfrom
Conversation
added 2 commits
April 9, 2026 18:15
Clarify how users start Aether after web installs and keep the devtest Windows installer in sync with the generated launcher flow.
lixfrank
requested review from
code-JDS,
shellmind112 and
yqmaphy
as code owners
code-JDS
approved these changes
Apr 9, 2026
shellmind112
approved these changes
Apr 9, 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
3 participants
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.
Issue for this PR
Closes #231
Type of change
What does this PR do?
This adds the missing devtest installer assets for macOS, Linux, and Windows, documents the download admin upload API, and updates the platform web installers so they tell users how to actually launch Aether after installation. It also keeps the Windows devtest installer aligned with the launcher behavior used by the generated installer flow.
How did you verify your code works?
I verified the installer and documentation changes by reviewing the generated script paths, launcher targets, and release-upload field mappings locally. I did not run automated tests because these changes are shell/batch scripts and docs only.
Screenshots / recordings
Not applicable.
Checklist