v2.4.3 preparation

[MrAnno]

Release Checklist

• Consider fixing
  • Build fails with LTO #524
  • Using any clause with double with at least one valid condition results in assertion failure #522
  • assertion for string should take const char * instead of char * #521
  • criterion 2.4.2 regression test failure against nanomsg 1.2.1 #518
  • Compilation warning: initialization discards 'const' qualifier from pointer target type #512
  • Compilation fails with clang-16: incompatible function pointer types initializing 'cookie_read_function_t *' (aka 'long (*)(void *, char *, unsigned long)') with an expression of type 'cr_retcount (void *, char *, cr_count)' (aka 'int (void *, char *, int)')  #503
  • Memory leak when using array type tags #501
• Release BoxFort with recent fixes:
  • FreeBSD sandbox: delivers SIGTERM/SIGKILL when parent exits same
  • context: Align object data to machine words
  • exe-mach: implement mach_vm_remap()-based patching of main()
• posix_spawnattr_setflags ASLR trick for macOS, since no_pie is no longer available for users on arm64 macOS.

Preparing release candidate

• Make sure bleeding builds on all platforms and all tests pass
• git checkout master
• git merge bleeding --no-commit --no-ff
• Bump project version (meson.build)
• Bump ABI version when needed (meson.build)
• Update ChangeLog
• git commit -m "release: v2.4.3"
• git tag -s v2.4.3-rc
• git push origin v2.4.3-rc master

After publishing the RC tag, each new push on master will produce a new release candidate.
The bleeding branch is fast-forwarded automatically during the RC period.

Finalizing release

After a 1-2 week RC period, the final version can be released:

• git checkout master
• git tag -s v2.4.3
• git push origin v2.4.3

[chenrui333]

Any timeline to cut a new release? Thanks!