Recent commits to derivepassphrase.git (61ebfcab313cfb49878b1f93ff3b53ae1255d48a)

Fix more details in the release checklist, after the fact

2025-06-24T22:28:10+02:00

Some details in the publishing of the documentation are slightly off.
</pre>

Update wishlist to post-v0.5.1

2025-06-24T22:09:38+02:00

</pre>

Release 0.5.1

2025-06-24T21:59:36+02:00

</pre>

Merge topic branch 'release-checklist' into master

2025-06-24T21:50:48+02:00

* release-checklist:
  Fix some details in the release checklist
</pre>

Fix some details in the release checklist

2025-06-24T21:48:33+02:00

The `bump-my-version` incantation was wrong, and actually already set up
for committing and tagging.
</pre>

Merge topic branch 'documentation-fixes' into master

2025-06-22T22:52:17+02:00

* documentation-fixes:
  Fix links to Windows SSH key support status elsewhere in the docs
</pre>

Fix links to Windows SSH key support status elsewhere in the docs

2025-06-22T22:50:07+02:00

Specifically, fix the links in the README and the reference section to
directly link to the wishlist, not the old GitHub issues.
</pre>

Merge topic branch 'changelog-v0.5' into master

2025-06-22T15:12:08+02:00

* changelog-v0.5:
  Add changelog entry for Python 3.14 support
  Assert compatibility with Python 3.14 (beta 3)
</pre>

Add changelog entry for Python 3.14 support

2025-06-22T15:10:18+02:00

</pre>

Assert compatibility with Python 3.14 (beta 3)

2025-06-22T14:39:43+02:00

Tested by manually installing Python 3.14 beta 3 and adjusting the
`hatch` testing matrix, because no published version of `hatch`
currently "knows" about Python 3.14 yet (i.e., provides Python 3.14
distributions for installation).

On Linux, the test suite runs decidedly slower because the default
`multiprocessing` start method changed from `fork` to `forkserver`, and
one test (`tests.test_derivepassphrase_cli.TestFakedConfigurationMutex`)
spawns hordes of processes, dominating the runtime.  This is
regrettable, but not strictly incompatible, and the obvious "fixes" are
actually policy decisions instead of behavioral fixes.  So I do not wish
to add any such fix just yet, without due consideration of the design
and the consequences.
</pre>