mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-31 22:14:25 +01:00
Garry Tanandcapy-ai[bot]
73f1394b0a
* fix(capy): the install trailer says behind=<n> and its fix, so a stale install shows in every relayed trailer (field list 2 item 13, #2378) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(capy): a lease records its holder's start identity, so a pid reused after a wake is reclaimed; a skipped session-start upgrade ends fail behind, never ok (GBRA-105, GBRA-106) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(lease): stale needs proof (unreadable or malformed identities keep the lease), ps identity is timezone-independent, and reclaim never deletes a concurrent renewal Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(lease): one directory lock for publish, prune and reclaim; reclaim rereads the record judged stale, so a renewal is never deleted or hidden Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(lease): the directory lock names its holder; broken only when the holder is dead or its pid reused, unlock removes only its own lock, touch exits 3 under a live holder Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(lease): breakers serialize on .lock.break and reread the lock before removing it; gstack-skill-start reports a lease the held lock kept out Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(lease): name the double-crash limit of breaking a dead lock Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * test(third-party-actions): the Aside drive-offer detector matches the product name, not the English idiom (paid run 38988927989 tpa-absent-linux false positive) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * docs(changelog): field list 2 F1 entry; capy/support.env GSTACK_MIN_REVISION to this release Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * chore: stamp v1.91.113.0 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
20 lines
1.3 KiB
Bash
20 lines
1.3 KiB
Bash
# capy/support.env — what the Capy skill bootstrapper (capy/skill/gstack/scripts/install.sh)
|
|
# reads from origin's default branch with `git show FETCH_HEAD:capy/support.env`,
|
|
# so a checkout too old to know today's rules learns them from the remote.
|
|
# Parsed, never sourced: KEY=<dotted number> lines only.
|
|
#
|
|
# GSTACK_MIN_REVISION: the floor. The oldest revision whose installer, trailer
|
|
# and fix lines are honest: below it the trailer fails (REVISION_BELOW_MINIMUM)
|
|
# and the bootstrapper fast-forwards a clean, unpinned checkout at install-mode
|
|
# session start (--check only reports). It is not the upgrade trigger: any
|
|
# checkout behind origin's default branch is fast-forwarded at install-mode
|
|
# session start by the checkout's own bin/gstack-capy-session (SELF_UPGRADE:
|
|
# lines; refusals skip and continue). Raise it only for install-honesty or
|
|
# security fixes, at stamp time, to the VERSION being released
|
|
# (docs/capy-install.md "Raising the supported minimum"); it never exceeds VERSION.
|
|
GSTACK_MIN_REVISION=1.91.113.0
|
|
# GSTACK_CAPY_MIN_WRAPPER: the oldest bootstrapper revision (GSTACK_CAPY_WRAPPER in
|
|
# capy/skill/gstack/scripts/install.sh) the owner should run. An older copy still
|
|
# works and prints an owner action (CAPY_WRAPPER_STALE).
|
|
GSTACK_CAPY_MIN_WRAPPER=1
|