Releases: osolmaz/unyolo
Release list
openclaw-unyolo v0.6.0
hf-broker/v0.8.0
unYOLO v0.5.0
What changed
This release completes the BrokerKit to unYOLO rename and raises reusable-grant capacity for high-volume work.
- The product, repository, Go module, command, environment variables, runtime paths, protocol namespace, and OpenClaw integration now use the unYOLO identity.
- Finite reusable grants support up to 1,000,000 uses.
- Reusable policies default to each provider operation's reviewed ceiling when use fields are omitted.
- Routine GitHub and Hugging Face windows can last up to seven days.
- Sensitive GitHub force, deletion, and tag operations keep their lower limits.
- Execution grants remain single-use, and larger budgets never broaden scope.
Upgrade note
This is a fresh-state replacement. There are no old names, aliases, state readers, or migration shims. Remove existing BrokerKit installations and state before installing unYOLO. Do not install this release over a running deployment.
openclaw-unyolo v0.5.1
What changed
openclaw-unyolo 0.5.1 aligns the OpenClaw plugin with unYOLO's high-volume reusable-grant contract.
- Operator V1 artifacts accept and validate finite grant budgets up to 1,000,000 uses.
- Approval and grant views support the updated reusable-use limits.
- Execution grants remain single-use, and approved scope is unchanged.
This package is published through npm trusted publishing from this release.
hf-broker v0.7.0
What changed
Hugging Face policies can now authorize large, tightly scoped repository and bucket jobs without asking for approval again on every request.
- Routine reusable operations default to up to 1,000,000 uses for as long as seven days.
- Omitted use counts now inherit the reviewed ceiling for the requested operation.
- Execution-bound operations remain single-use.
- Larger budgets do not broaden the approved client, operation, target, path, key, or attributes.
- The finite-use limit is validated consistently across policy parsing, grants, storage, Operator V1, MCP, and generated clients.
Upgrade note
This release changes the pre-release v1 state contract in place. It does not migrate existing broker state. Remove the existing installation and use fresh state before installing this version. Do not install it over a running deployment.
gh-broker v0.5.0
What changed
GitHub policies can now authorize large, tightly scoped repository jobs without asking for approval again on every request.
- Routine reusable operations default to up to 1,000,000 uses for as long as seven days.
- Omitted use counts now inherit the reviewed ceiling for the requested operation.
- Force pushes, ref deletions, and tag updates remain limited to 25 uses for one hour.
- Execution-bound operations remain single-use.
- Larger budgets do not broaden the approved client, operation, repository, ref, path, or attributes.
- The finite-use limit is validated consistently across policy parsing, grants, storage, and Operator V1.
Upgrade note
This release changes the pre-release v1 state contract in place. It does not migrate existing broker state. Remove the existing installation and use fresh state before installing this version. Do not install it over a running deployment.
sudo-broker/v0.3.1
What's Changed
Full Changelog: brokerkit/v0.4.2...sudo-broker/v0.3.1
brokerkit/v0.4.2
What's Changed
Full Changelog: brokerkit/v0.4.1...brokerkit/v0.4.2
brokerkit/v0.4.1
What's Changed
Full Changelog: brokerkit/v0.4.0...brokerkit/v0.4.1
brokerkit/v0.4.0
What's Changed
Full Changelog: hf-broker/v0.6.2...brokerkit/v0.4.0