Recent commits to derivepassphrase.git (99863c4d7b2a3ee8f7b0d0d3e3f924afe7d40fb8)

Reformat everything with ruff

2024-07-21T10:09:10+02:00

</pre>

Fix style issues with ruff (hatch default configuration)

2024-07-20T23:46:05+02:00

Because `ruff` only shows online documentation for the latest version,
it is inconvenient to work with outdated rulesets.  So, manually update
the `hatch` configuration from `ruff` v0.4.5 to v0.5.0, and reimplement
all rule changes by hand.
</pre>

Fix style issues with ruff (in its default configuration)

2024-07-19T18:58:12+02:00

(One of them actually was a bug: an f-string missing the leading `f`.)
</pre>

Release 0.1.1

2024-07-14T16:14:59+02:00

</pre>

Set up a web host for the documentation

2024-07-14T16:11:25+02:00

</pre>

Remove CSS file mention in MkDocs configuration

2024-07-14T16:10:32+02:00

The file itself was already removed in
cedd14e7792ab8b3a7cc1bfe0b2d5e280695cd40.
</pre>

Update package dependencies in README

2024-07-14T15:23:27+02:00

We erroneously claim that we require Python 3.11 instead of 3.10, and we
neglect to mention the typing-extensions package.
</pre>

Restore version attributes in modules

2024-07-14T15:00:43+02:00

Version 0.1.0 included broken references to the `__version__` attribute
in other modules, most importantly in the command-line interface.  In
the README, we mention that we support copying the files into the target
directory.  The command-line interface will then have no installed
package to query for its version number.

Fix this by re-duplicating the version number in the `__version__`
attribute, manually, across all top-level modules.

In the long run, we either want Hatchling to support writing the version
back to multiple files, or we want to write a script or hook script that
accomplishes this ourselves, or perhaps we want to publish `sequin` and
`ssh_agent_client` as separate packages so they get their own version
number.  Until then, manually duplicating the number to the top-level
modules is an acceptable compromise to me.
</pre>

Release 0.1.0

2024-07-14T13:17:54+02:00

</pre>

Set project version statically due to Hatchling limitation

2024-07-14T13:14:10+02:00

Hatch/Hatchling do not support reading the version string from (or
writing a new string to) multiple files.  See
[pypa/hatch#684](https://github.com/pypa/hatch/issues/684).  Until such
a feature is implemented, or I write my own script or hatchling plugin
to replicate the version number myself, set the number statically in the
project metadata, and forego the luxury of having the version number
available in source code form.  Users wanting the project version number
will need to query the package metadata, e.g. via
`importlib.metadata.version(...)` from the Python standard library.
</pre>