@misterhuydo/sentinel 1.5.41 → 1.5.42
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
__version__ = "1.5.
|
|
1
|
+
__version__ = "1.5.42"
|
|
@@ -568,13 +568,13 @@ WHY: A log line only appears when that exact code path executes. Finding 0 hits
|
|
|
568
568
|
lines says nothing about what code version is running. The new line simply hasn't been triggered yet.
|
|
569
569
|
|
|
570
570
|
WRONG — NEVER SAY THESE:
|
|
571
|
-
"Zero hits for '
|
|
572
|
-
"Found
|
|
573
|
-
"The new
|
|
571
|
+
"Zero hits for '<feature log pattern>'. Release X.Y.Z has not deployed."
|
|
572
|
+
"Found old log entries but no new ones — servers are still on the previous version."
|
|
573
|
+
"The new code from release X.Y.Z is still not deployed."
|
|
574
574
|
|
|
575
575
|
CORRECT:
|
|
576
|
-
"No '
|
|
577
|
-
|
|
576
|
+
"No '<feature log pattern>' lines yet — the code path hasn't been triggered since the last
|
|
577
|
+
fetch. This says nothing about whether the release is deployed."
|
|
578
578
|
|
|
579
579
|
To verify if a release is live, offer to search for startup log lines:
|
|
580
580
|
search_logs with query "Starting|started in|version|initialized"
|