Skip to content

Releases: capeprivacy/pycape

v3.1.1

30 Mar 19:36
23333d0
Compare
Choose a tag to compare

What's Changed

v3.1.0

17 Feb 18:29
10e28df
Compare
Choose a tag to compare

AWS cert chains have a 3hr expiry, so using Cape keys that were generated >3hrs ago will fail while verifying the cert chain. We're temporarily skipping this for cape.key because that's the only affected client method. We're working on a better fix and will re-release when that lands.

What's Changed

  • skip cert chain verification for now on key route (#119) @justin1121
  • add section about updating pydocs to releasing doc (#115) @jvmncs

v3.0.0

08 Feb 17:16
542cc96
Compare
Choose a tag to compare

Breaking Changes

Function tokens have been removed from latest versions of Cape SDKs; the new authentication method is to use personal access tokens. Technically this introduces a feature regression, since PATs give access to a user's entire set of deployed functions. A future update will allow PATs to be scoped to only authenticate run requests for specific functions, which will bring back parity with the function token approach.

What's Changed

  • bump cryptography to resolve security alert (#117) @jvmncs
  • bump dependencies, resolving some dependabot warnings (#116) @jvmncs
  • fix docsite logo and missing cape_encrypt api ref (#114) @jvmncs
  • refactor pycape api to use PATs, not fn tokens (#113) @jvmncs
  • small fix to Cape.key response handler (#112) @jvmncs

v2.1.0

02 Feb 16:19
41ec041
Compare
Choose a tag to compare

What's Changed

v2.0.0

04 Oct 16:50
Compare
Choose a tag to compare

Breaking Changes

As of #96, a function ID is no longer sufficient to connect to a Cape function. Whenever one intends to use a Cape function, they must pass a fully-specified pycape.FunctionRef (which now requires both function ID and function token). The idiomatic way of doing this is to load the FunctionRef from JSON (see examples).

Previously, one could supply function ID strings instead of the full FunctionRef. For example, the following two code snippets were equivalent:

# Method 1
cape.connect("sa15lcf12td45s1")
cape.close()

# Method 2
fref = pycape.FunctionRef("sa15lcf12td45s1")
cape.connect(fref)
cape.close()

The breaking change is that Method 1 is now forbidden and will yield a TypeError if attempted.

What's Changed

v1.1.0

21 Sep 19:23
Compare
Choose a tag to compare

What's Changed

1.0.0

18 Aug 00:13
Compare
Choose a tag to compare

Initial Release