detangle 0.2.6

Behavior change: affected --since <ref> now compares from the merge-base of <ref> and HEAD, not the tip of <ref>, so commits that landed on <ref> after your branch no longer count as changes. Untracked files are included, and deleted files and config changes are listed on stderr (not followed). Scripts may see fewer modules than before. In a shallow CI checkout, fetch history (with actions/checkout, fetch-depth: 0); a missing ref or merge-base is now an error rather than a wrong list.

Also in 0.2.6: a tsconfig whose extends package isn't installed keeps its own paths and baseUrl, with a note naming the missing base (#32).

What's Changed

• npm: lock the published 0.2.5 platform packages by @debug-diary-1 in #33
• README and site: list every default rule by @debug-diary-1 in #31
• Keep a tsconfig's own paths when its extends can't be loaded by @debug-diary-1 in #32
• Release 0.2.6: a tsconfig keeps its own paths when its extends can't be loaded by @debug-diary-1 in #34
• affected --since: compare from the merge-base, and say what isn't followed by @debug-diary-1 in #35

Full Changelog: v0.2.5...v0.2.6