Skip to main content

Changelog

Find the release date of a Permit.io API, SDK method, Permit Elements feature, or policy decision point (PDP) change. This page names the source that covers each period and links to it. It is for developers who need a release date before they upgrade a dependency or plan work that depends on a capability.

The Canny changelog has no entries after May 2024

The newest entry on the Permit.io Canny changelog is dated May 16, 2024. A capability released after that date has no entry there, so a missing entry on Canny is not evidence that a capability doesn't exist. For anything released after May 2024, read the SDK and PDP release notes on GitHub, or check the Permit.io API reference, which reflects the API that Permit serves today.

Where to look up a release

SourceWhat it covers
Permit.io changelog on CannyProduct updates published between October 2023 and May 2024. Each entry has a date, a title, and a description. The newest entry, dated May 16, 2024, covers the getAuthorizedUsers() SDK method.
permit-node releases, permit-python releases, permit-golang releases, permit-java releases, permit-dotnet releases, permit-ruby releasesThe version that added each SDK method, per language, with the release date on every tag
PDP releasesChanges to the Edge PDP image permitio/pdp-v2, including new endpoints and configuration variables
Permit CLI releasesCommands and flags added to the Permit CLI
Permit.io API referenceThe endpoints, parameters, and response schemas that the Permit API serves now

Confirm that a capability is available to you

A release date tells you when Permit shipped a capability, not whether your installation has it. To confirm that your setup can use it:

  1. Read the release notes of the source above that owns the capability, and note the version that introduced it.
  2. Compare that version with the version you run. For an SDK, read the resolved version in your lock file or package manifest. For a self-hosted PDP, read the image tag in your container or Helm configuration.
  3. Call the capability against your environment. A 404 from the Permit API or a missing SDK method means your version predates the change.

An upgrade to the version named in the release notes, followed by a successful call, confirms that the capability is available.