Recent commits to derivepassphrase.git (29a9a974a1bb939863ca5cb1f7646581526b482f)

Compile changelog for v0.5

2025-06-15T09:30:13+02:00

(Oops.)
</pre>

Update wishlist to post-v0.5

2025-06-14T22:13:51+02:00

</pre>

Release 0.5

2025-06-14T21:41:32+02:00

</pre>

Merge topic branch 'project-config-and-script-fixes' into master

2025-06-14T21:35:47+02:00

* project-config-and-script-fixes:
  Update the man page diagnostic script: settings and output format
  Fix bump-my-version config to what derivepassphrase actually uses
</pre>

Update the man page diagnostic script: settings and output format

2025-06-14T20:07:44+02:00

Update the man page diagnostic script to current settings: use the
updated path to the man pages, and use metavars without the `!s`
conversion. Additionally, since the output is currently a diagnostic on
standard error, and very verbose, emit a terser shorthand notation to
standard output instead. (Also sort the files to be examined first.)
</pre>

Fix bump-my-version config to what derivepassphrase actually uses

2025-06-14T19:05:26+02:00

The version scheme did not match the actual pre-release version number
formatting, the search-/replace-patterns overlapped, and the man pages
were being searched for in the wrong directory.
</pre>

Merge topic branch 'coverage-slipups' into master

2025-06-14T16:51:56+02:00

* coverage-slipups:
  Fix some coverage slipups
</pre>

Merge topic branch 'pin-testing-dependencies' into master

2025-06-14T16:49:39+02:00

* pin-testing-dependencies:
  Pin testing dependencies
</pre>

Fix some coverage slipups

2025-06-10T19:31:24+02:00

The first slipup deals with two different wrappers around `os.getenv`,
depending on whether the system support bytes-based environment
variables. We care about whether the wrapper function (whichever
implementation) is called correctly, not which wrapper function is
selected. So, rewrite the branch to put the system-specific definitions
under coverage exclusion, and the rest not.

The second slipup concerns the concurrency limit. The detection is
system- and runtime-dependent, but the error paths were previously not
excluded from coverage. Additionally, we claimed to manually support the
`PYTHON_CPU_COUNT` environment variable on Python 3.12, but contained no
matching code. So, rewrite the code to add that missing support, in
a coverage-friendly way.
</pre>

Merge topic branch 'defer-automatic-color-support' into master

2025-06-09T23:03:12+02:00

* defer-automatic-color-support:
  Document the removal/deferring of automatic color support
  Remove automatic color and text styling support
</pre>