Repository navigation
chore: a script's version is the UTC time it changed, written as ISO 8601 - #166
Open
kurtseifried wants to merge 1 commit into
Open
kurtseifried wants to merge 1 commit into
kurtseifried wants to merge 1 commit into
Conversation
…8601 (2026-10-26T15:12Z)
Replaces the YYYY.MMDDHHMM form ("2026.10260504"), which looked like a version number but
was a squashed timestamp. All eleven scripts move to 2026-10-26T15:12Z, and the banner and
debug-log lines drop the "v" in front of it, since a time is not a version number.
check-script-versions.py now compares versions as UTC times. It still READS the old form,
so this switch is itself checked as moving forwards, but it refuses the old form as a new
value so it cannot creep back. Its self-tests cover the switch, an earlier ISO time, month
and year rollovers, and near misses (seconds, a lower-case z, an offset).
ENGINEERING.md, CLAUDE.md, AGENTS.md and periodic-sweep.md describe the new form; the last
also had it wrong before (YYYY.MMDDHHSS).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Asked for 2026-10-26: "lets drop that goofy year.whatever and just go with a timestamp", and the choice was ISO 8601 UTC, to the minute.
SCRIPT_VERSION/$ScriptVersion"2026.10260504""2026-10-26T15:12Z"… Windows Update v2026.10260504… Windows Update 2026-10-26T15:12Z--- windows-update v2026.10260504 ------ windows-update 2026-10-26T15:12Z ---csa-claude-connectors.pyincluded), and the banner and log lines drop thev.tools/check-script-versions.pycompares versions as UTC times. It still readsYYYY.MMDDHHMM, so this switch is itself checked as moving forwards (it reported "all 10 changed scripts bumped"). It refuses the old form as a new value, so the old form can't come back. New self-tests cover the switch, an earlier ISO time, month and year rollovers, and near misses: seconds, a lower-casez, an offset.ENGINEERING.md(the format and the one-liner that prints it),CLAUDE.md,AGENTS.md,docs/periodic-sweep.md. The last one had the old format wrong as well (YYYY.MMDDHHSS).archives/and resumption summaries, which record what was true at the time.Test plan
check-script-versions.py: self-tests pass, and the checker passes on this diff../tools/check-all.sh: everything passes except the 3 macOS checks that fail on a Windows host before and after this change (check-all.sh is red on a Windows host: three macOS desktop-app checks build Windows paths for bash #163). Pester 79/79, PowerShell parse, PSScriptAnalyzer and bash-nall pass.🤖 Generated with Claude Code