From c8aebd3c7179c88a9754d74adff60c4c19a3ec74 Mon Sep 17 00:00:00 2001 From: Steven Janzou Date: Sun, 10 Dec 2023 23:09:34 -0700 Subject: [PATCH] 2023.12.17.ssc.288 release candidate no expiration --- deploy/runtime/versions.lk | 2 +- src/main_add.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy/runtime/versions.lk b/deploy/runtime/versions.lk index 0b6698da40..1dc03288aa 100644 --- a/deploy/runtime/versions.lk +++ b/deploy/runtime/versions.lk @@ -51,7 +51,7 @@ Some more examples: //*********************************************************************************************************************************************************** //CURRENT WORKING VERSION (see SAM/main_add.h) - CHANGE THIS VERSION NUMBER WHEN RELEASES ARE CREATED AND MAKE A NEW CURRENT WORKING VERSION FUNCTION -version_upgrade{'2023.10.31'} = define() { +version_upgrade{'2023.12.17'} = define() { const cfg = config(); diff --git a/src/main_add.h b/src/main_add.h index 4823a8787a..3b6f71c560 100644 --- a/src/main_add.h +++ b/src/main_add.h @@ -74,7 +74,7 @@ static SamApp::ver releases[] = { //intermediate version numbers are required in this list in order for the version upgrade script (versions.lk) to work correctly //please clarify the reason for the new version in a comment. Examples: public release, variable changes, internal release, public beta release, etc. //the top version should always be the current working version - { 2023, 12, 17 }, + { 2023, 12, 17 }, // 2023.12.17 ssc 288 release candidate from develop - no expiration first built 12/11/2023 { 2023, 12, 1 }, // 2023.12.1 ssc 287 2023 release candidate from develop expires 12/17/2023 { 2023, 10, 31 }, // 2023.10.31 ssc 286 public beta release from develop expires 11/30/2023 { 2023, 10, 6 }, // 2023.10.6 ssc 285 beta release from develop with hybrids expires 1/6/2024