The first of May, an open source release again, and a pin from April 2024 that could finally be removed.
the decision record from 2024 listed four triggers.
none of them fired. this is a fifth, and it is the
opposite of what the record anticipated.
pinned: 7.2.4, for thirteen months
now: 8.0, unpinned to ^8.0
the fork: still installed in the compatibility job,
still passing, and now a preference
rather than an escape route
thirteen months of a monthly job to keep an option open
that resolved on its own.
A decision record that enumerates triggers cannot anticipate the situation resolving itself, which is a real limitation and not a fault — the alternative is a record with no triggers at all. The thirteen months of a scheduled job is the cost of the option, and it is small enough that the same choice would be right again.