v0.2.0-rc3: the launcher's third candidate, the first signed and the first that reads the game
\nThe Phaethon launcher installed from Setup.exe and updated in place through Velopack, now\nsigned with an Azure Artifact Signing identity, so Windows names the publisher and SmartScreen\ncan build reputation on it. While a game the launcher started runs, the Game page and the\nDiscord presence say what the player is doing, read from the runtime's session journal (at the\ntitle, in the menus, racing on a named track, in a cutscene), play time is credited from it, each\ngame keeps its last session, and the exit toast says how the session went.
\nSince v0.2.0-rc2: the session reader, the status, the play time and the last session on the\nGame page; the Discord presence and the exit toast reading the session; the download's presence\nkeeping the same floor; settings schema four; the tree naming alex/phaethon-launcher and\nalex/phaethon; the release job signing through the identity's six values.
\nThis candidate needs the runtime at v0.1.0-rc3 or later for the journal; against an older\nruntime it shows what rc2 showed.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc3","Type":"Delta","FileName":"PhaethonLauncher-0.2.0-rc3-delta.nupkg","SHA1":"9D1C9F412731FDE8AD208021E8407AF563A197AE","SHA256":"7FA576B74C5F05988EFA56E5E0945F0C29EA0A4183F2BDF75076E9D95FB7F43C","Size":554674,"NotesMarkdown":"v0.2.0-rc3: the launcher's third candidate, the first signed and the first that reads the game\n\nThe Phaethon launcher installed from Setup.exe and updated in place through Velopack, now\nsigned with an Azure Artifact Signing identity, so Windows names the publisher and SmartScreen\ncan build reputation on it. While a game the launcher started runs, the Game page and the\nDiscord presence say what the player is doing, read from the runtime's session journal (at the\ntitle, in the menus, racing on a named track, in a cutscene), play time is credited from it, each\ngame keeps its last session, and the exit toast says how the session went.\n\nSince v0.2.0-rc2: the session reader, the status, the play time and the last session on the\nGame page; the Discord presence and the exit toast reading the session; the download's presence\nkeeping the same floor; settings schema four; the tree naming alex/phaethon-launcher and\nalex/phaethon; the release job signing through the identity's six values.\n\nThis candidate needs the runtime at v0.1.0-rc3 or later for the journal; against an older\nruntime it shows what rc2 showed.\n\nsigned: true","NotesHTML":"v0.2.0-rc3: the launcher's third candidate, the first signed and the first that reads the game
\nThe Phaethon launcher installed from Setup.exe and updated in place through Velopack, now\nsigned with an Azure Artifact Signing identity, so Windows names the publisher and SmartScreen\ncan build reputation on it. While a game the launcher started runs, the Game page and the\nDiscord presence say what the player is doing, read from the runtime's session journal (at the\ntitle, in the menus, racing on a named track, in a cutscene), play time is credited from it, each\ngame keeps its last session, and the exit toast says how the session went.
\nSince v0.2.0-rc2: the session reader, the status, the play time and the last session on the\nGame page; the Discord presence and the exit toast reading the session; the download's presence\nkeeping the same floor; settings schema four; the tree naming alex/phaethon-launcher and\nalex/phaethon; the release job signing through the identity's six values.
\nThis candidate needs the runtime at v0.1.0-rc3 or later for the journal; against an older\nruntime it shows what rc2 showed.
\nsigned: true
"},{"PackageId":"PhaethonLauncher","Version":"0.2.0-rc2","Type":"Full","FileName":"PhaethonLauncher-0.2.0-rc2-full.nupkg","SHA1":"43B941447C25665BD1304ACEA872285B2A471894","SHA256":"943AC1C4EE7D2CE26027F9B03E9B96BE01AE48ABEC90E961CC934825E68160F1","Size":65874649,"NotesMarkdown":"v0.2.0-rc2: the launcher's second candidate, the first with the installer\n\nThe Phaethon launcher installed rather than dropped: PhaethonLauncher-win-Setup.exe installs it\nper user under the player's local programs folder with a Start Menu shortcut and an Apps and\nFeatures entry, and it updates itself in place through Velopack against the store's feed. The\nexecutable, the window, the shortcuts and the entry say Phaethon, and the first start copies the\nold JakLauncher folder into %AppData%\\PhaethonLauncher and leaves the old one for one version.\n\nSince v0.2.0-rc1: the installer and the update path, the name, the data folder's migration, the\npre-release comparison that offers rc2 to rc1, the release job packing with vpk and publishing\nSetup.exe, the packages and the feed, the signing wiring that signs once its identity exists and\npublishes unsigned with a warning until then, and the store publisher for the feed.\n\nThis candidate is unsigned; SmartScreen warns before Setup.exe runs. The pack id is new, so rc1's\nbare exe does not update into this: install it from Setup.exe.\n\nsigned: false","NotesHTML":"v0.2.0-rc2: the launcher's second candidate, the first with the installer
\nThe Phaethon launcher installed rather than dropped: PhaethonLauncher-win-Setup.exe installs it\nper user under the player's local programs folder with a Start Menu shortcut and an Apps and\nFeatures entry, and it updates itself in place through Velopack against the store's feed. The\nexecutable, the window, the shortcuts and the entry say Phaethon, and the first start copies the\nold JakLauncher folder into %AppData%\\PhaethonLauncher and leaves the old one for one version.
\nSince v0.2.0-rc1: the installer and the update path, the name, the data folder's migration, the\npre-release comparison that offers rc2 to rc1, the release job packing with vpk and publishing\nSetup.exe, the packages and the feed, the signing wiring that signs once its identity exists and\npublishes unsigned with a warning until then, and the store publisher for the feed.
\nThis candidate is unsigned; SmartScreen warns before Setup.exe runs. The pack id is new, so rc1's\nbare exe does not update into this: install it from Setup.exe.
\nsigned: false
"}]}