Repository navigation
Lockkeeper 1.3.0
A fresh pip install lockkeeper now works out of the box, Lockkeeper moves to the
Functional Source License, and telemetry asks once instead of staying silent.
License
- Lockkeeper is now licensed under the Functional Source License, Version 1.1, ALv2
Future License
(FSL-1.1-ALv2). You can use, modify and share it for any purpose, including at work
and on commercial projects, except offering it, or a product built from it, as a
competing commercial product or service. Each release becomes Apache 2.0 two years
after it ships. Releases up to and including 1.2.0 remain under the MIT license.
New
- Telemetry asks once.
lockkeeper initandlockkeeper hooks installask whether to
share anonymous daily usage counts (Enter means yes), only in an interactive
terminal, never in scripts or CI or whenDO_NOT_TRACKis set, and never again once
answered. It stays off until you say yes. See
docs/TELEMETRY.md. - The README, the one-prompt installer and the Windows notes install from PyPI:
pipx install lockkeeper,lockkeeper init,lockkeeper rebuild. - Releases run from Actions → publish → Run workflow: it uploads to PyPI, then
creates the tag and GitHub release with the CHANGELOG notes, and it refuses a commit
it couldn't tag before uploading anything. See
docs/RELEASING.md.
Fixed
- A fresh
pip install lockkeepercould not build its index:rebuildandroute
failed with "Required runtime snapshot is missing" untillockkeeper snapshot-runtimeswas run (a git checkout hid it with seeded placeholders). They
now capture the agent inventories themselves, or start from empty ones if the
agents' CLIs fail. On 1.2.0, runlockkeeper snapshot-runtimesonce first. CI now
installs the built package into a brand-new home and routes a task.