Changes to the SDKs, the CLI, the API, the customer portal, the dashboard and the website. Filter by what you use, or follow it in a reader with the Atom feed.
The Electron, .NET, Rust, Swift, C++ and Flutter SDKs and the keygrant command line reach their first stable release. Nothing changed in how they work: move your version constraint to 1.x, and a C++ app's find_package now asks for keygrant 1.0.
Turn on Key pickup for a product and your app can restore a customer's license with a code sent to the email they bought with, no key to type, as App Store builds need. Call restoreByEmail(email, code) after pickUp(email).
From CLI 0.5.2, the Windows keygrant file on the release page is signed with Authenticode.
From CLI 0.5.1, the macOS keygrant files on the release page are signed with a Developer ID and notarized by Apple.
keygrant licenses user-lock <key> <off|email|code> sets who can activate a new device on a key. licenses get and products now show who can activate.
keygrant licenses test --scenario used-up makes a test license whose first meter has no uses left, so you can see how your app handles it.
Each CLI release now attaches the keygrant command as one file for Linux, macOS and Windows on its GitHub release page. It reads your key from KEYGRANT_API_KEY.
keygrant licenses uses can now set whether a meter comes back each billing period (--resets) and take a meter off a key (--remove).
keygrant licenses issue --meter exports=1000 gives a new key meters of its own in place of its model's, and --no-meters gives it none.
keygrant licenses devices <key> lists the devices a license is active on, with the activation id that keygrant licenses free-device takes.
keygrant licenses get says whether a key is typed, sent as a key file or sent as a license file, and keygrant products says which models send files.
Sell a feature a set number of times. A license model can count uses of an export or a render, per key or per billing period, and the app spends them with use(meter, n). Online a spend is exact; offline it comes from a small allowance, so an outage never locks out a paying customer.
A license model can send its key as a signed file buyers drop onto your app, or as an offline license file that works with no connection at all. Buyers can download the file again from the customer portal, and keygrant licenses file fetches it from the CLI.