3.22.1 release tracker

[shonfeder]

Preparation

• Create release candidate branch 3.22.1-rc from last point tag 3.22.1-1
• Open release draft PR from branch 3.22.1-rc into main: [3.22.1] release #13947

Fixes

Regressions requiring fixes in main and backports to 3.22.1-rc:

• dune 3.22.0 bootstrap fails on Windows < 8 — GetSystemTimePreciseAsFileTime not found in KERNEL32.dll #13871
  • fix time_stubs.c: add fallback for Windows 7 #13905
  • followup fix for warning fix(time): address warning on Windows in time_stubs.c #13914
  • backported via PRs
    • [3.22.1] backport #13905 #13941
    • [3.22.1] backport #13914 #13946
• 3.22.0 does not build on systems without clock_gettime: how better to fix it? #13917
  • NOTE: Depends on the Windows 7 fixes above.
  • fix fix(time): old macos fallback #13918
  • backported via PR [3.22.1] backport #13918 #13948
• dune trace cat --chrome-trace has wrong timing units #13906
  • repro test: chrome trace timestamp magnitude #13907
  • fix fix(trace): use microseconds for chrome trace timestamps #13911
  • backported via PR [3.22.1] backport #13911 #13949
• 3.22.0 crash due to an internal error #13904
  • repro test(runtest): dune test without a default context #13913
  • fix(runtest): don't run in all contexts #13930
  • backported via PR #[3.22.1] Backport #13930 #13980

Release

• opam repo publication PR: [new release] dune (18 packages) (3.22.1) opam-repository#29632
• After opam-ci results are available, Review revdeps diff and diagnose any
  new failures: [new release] dune (18 packages) (3.22.1) opam-repository#29632 (comment)
• merge opam repo PR (or address problems and cut a new release)

Post-release

• Merge release branch into main [link to dune PR]
• Write a post about the release on Discuss: https://discuss.ocaml.org/t/ann-dune-3-22/17912/2
• Announce on ocaml.org: Announce dune 3.22.1 ocaml.org#3596
• Store the revdeps error file in the logs as HTML

[shonfeder]

@Alizter just reported that #13891 does not need to be included in this release. There is a regression in behavior to be fixed there, but it will be done in a followup release.