v0.2.0-rc5: the launcher's fifth candidate, with an account, a live Home page and a setup of its own
\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, and now signing its player in\nto Phaethon.
\nSince v0.2.0-rc4: the sign-in through Phaethon's realm with a device code and the profile page\nbehind it; the Home page showing the running game's session while the library waits for it to\nend; the first-run setup rewritten for Phaethon with an account step and a presence switch in\nSettings; a runtime download the store republishes under starting over instead of leaving a\nmixed install, with each runtime version in its own folder in the store; the wizard's license\npage filling its box with the full terms, the uninstaller in the wizard's frame, the splash and\nAbout showing the tag's version, the Server field gone, the changelog modal wider and its entries\none line each; the extractor's failed build named plainly.
\nThis candidate reads the runtime at v0.1.0-rc5 or later and signs in against the phaethon realm\nonce it is applied; without the realm, Sign In reports that it could not be reached.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc5","Type":"Delta","FileName":"PhaethonLauncher-0.2.0-rc5-delta.nupkg","SHA1":"7B1281728C065283BADB010B790C316A1D2A2D21","SHA256":"A8138790E6555F2EF36890EC1302C969DF6AEB7F4DE61C39D11AE00FA56991F2","Size":605959,"NotesMarkdown":"v0.2.0-rc5: the launcher's fifth candidate, with an account, a live Home page and a setup of its own\n\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, and now signing its player in\nto Phaethon.\n\nSince v0.2.0-rc4: the sign-in through Phaethon's realm with a device code and the profile page\nbehind it; the Home page showing the running game's session while the library waits for it to\nend; the first-run setup rewritten for Phaethon with an account step and a presence switch in\nSettings; a runtime download the store republishes under starting over instead of leaving a\nmixed install, with each runtime version in its own folder in the store; the wizard's license\npage filling its box with the full terms, the uninstaller in the wizard's frame, the splash and\nAbout showing the tag's version, the Server field gone, the changelog modal wider and its entries\none line each; the extractor's failed build named plainly.\n\nThis candidate reads the runtime at v0.1.0-rc5 or later and signs in against the phaethon realm\nonce it is applied; without the realm, Sign In reports that it could not be reached.\n\nsigned: true","NotesHTML":"v0.2.0-rc5: the launcher's fifth candidate, with an account, a live Home page and a setup of its own
\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, and now signing its player in\nto Phaethon.
\nSince v0.2.0-rc4: the sign-in through Phaethon's realm with a device code and the profile page\nbehind it; the Home page showing the running game's session while the library waits for it to\nend; the first-run setup rewritten for Phaethon with an account step and a presence switch in\nSettings; a runtime download the store republishes under starting over instead of leaving a\nmixed install, with each runtime version in its own folder in the store; the wizard's license\npage filling its box with the full terms, the uninstaller in the wizard's frame, the splash and\nAbout showing the tag's version, the Server field gone, the changelog modal wider and its entries\none line each; the extractor's failed build named plainly.
\nThis candidate reads the runtime at v0.1.0-rc5 or later and signs in against the phaethon realm\nonce it is applied; without the realm, Sign In reports that it could not be reached.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc4","Type":"Full","FileName":"PhaethonLauncher-0.2.0-rc4-full.nupkg","SHA1":"263E6D4589E9D62BAB5B500F94783A30776D5100","SHA256":"92D785760DCA661AEA2290327F9A31BE9EF2AB3DA80E0B332937DD6857AE58C8","Size":65960599,"NotesMarkdown":"v0.2.0-rc4: the launcher's fourth candidate, the first with a wizard and two changelogs\n\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, reading the game's session\njournal while it runs, and now aware of what a runtime update reaches.\n\nSince v0.2.0-rc3: the install wizard with its license, its read-only location, its progress\nand its launch box, which says whether it installs, updates, reinstalls or replaces and\nrefuses while the launcher runs, and one Apps and Features entry whose uninstaller asks what\nelse to remove; the two changelogs, the launcher's and the runtime's, read as markdown from\nthe store in two tabs; a runtime update that rebuilds only the games and stages whose build\ninputs changed, from the keys the runtime's manifest carries, with Play running the rebuild\nfirst; the Discord presence under the Phaethon application's id; a download the store answers\nwith 429 or 503 waiting and asking again; the extractor's exit 4003 worded and 4001 corrected.\n\nThis candidate reads the rebuild keys and the runtime changelog from a runtime at v0.1.0-rc4 or\nlater; against an older runtime it rebuilds every imported game once per runtime version, as\nupstream's launcher does, and the Runtime tab says no changelog is published.\n\nsigned: true","NotesHTML":"v0.2.0-rc4: the launcher's fourth candidate, the first with a wizard and two changelogs
\nThe Phaethon launcher installed from a wizard around Velopack's Setup.exe, updated in place\nthrough Velopack, signed with an Azure Artifact Signing identity, reading the game's session\njournal while it runs, and now aware of what a runtime update reaches.
\nSince v0.2.0-rc3: the install wizard with its license, its read-only location, its progress\nand its launch box, which says whether it installs, updates, reinstalls or replaces and\nrefuses while the launcher runs, and one Apps and Features entry whose uninstaller asks what\nelse to remove; the two changelogs, the launcher's and the runtime's, read as markdown from\nthe store in two tabs; a runtime update that rebuilds only the games and stages whose build\ninputs changed, from the keys the runtime's manifest carries, with Play running the rebuild\nfirst; the Discord presence under the Phaethon application's id; a download the store answers\nwith 429 or 503 waiting and asking again; the extractor's exit 4003 worded and 4001 corrected.
\nThis candidate reads the rebuild keys and the runtime changelog from a runtime at v0.1.0-rc4 or\nlater; against an older runtime it rebuilds every imported game once per runtime version, as\nupstream's launcher does, and the Runtime tab says no changelog is published.
\nsigned: true
"}]}