Skip to content

Releases: chipsalliance/caliptra-sw

release_v20240202_0

02 Feb 12:22
b39277c
Compare
Choose a tag to compare
fpga-image: Move gdb dependencies from VM to SD image (#1307)

release_v20240201_0

01 Feb 12:22
Compare
Choose a tag to compare
Add certify_key_csr integration test

With this test, Runtime coverage shoots up to 82.59488% from
~75%.

release_v20240126_0

26 Jan 13:48
Compare
Choose a tag to compare
Test that attestation fails after calling DisableAttestation

release_v20240125_0

25 Jan 11:56
Compare
Choose a tag to compare
Update chrono from 0.4.24 to 0.4.32.

This removes the time-0.1 dependency, resolving
https://github.com/chipsalliance/caliptra-sw/security/dependabot/4.

release_v20240124_0

24 Jan 13:51
Compare
Choose a tag to compare
Update chrono from 0.4.24 to 0.4.32.

This removes the time-0.1 dependency, resolving
https://github.com/chipsalliance/caliptra-sw/security/dependabot/4.

release_v20240123_0

23 Jan 12:23
Compare
Choose a tag to compare
Do not borrow mbox from drivers during the mbox_responder loop.

This allows future commands to call helpers that borrow `drivers`.

In addition, add helpers for reading requests / writing responses, for brevity.

release_v20240120_0

20 Jan 13:46
e5ddf7f
Compare
Choose a tag to compare
CI: Update Caliptra RTL (#1282)

release_v20240119_0

19 Jan 12:23
54b3be7
Compare
Choose a tag to compare
nightly-release: Fix rtl-repo-sync permission error. (#1280)

Whoops, #1271 broke the nightly build:

```
github/workflows/nightly-release.yml (Line: 10, Col: 3):
Error calling workflow
'chipsalliance/caliptra-sw/.github/workflows/rtl-repo-sync.yml@d51627a91130c6d5f7c1151ab0e5304e9153753a'.
The workflow is requesting 'contents: write, pull-requests: write',
but is only allowed 'contents: read, pull-requests: none'.
```

Give the rtl-repo-sync job the necessary permissions to create the
pull-request.

rom-1.0.0

12 Jan 10:44
Compare
Choose a tag to compare

release_v20240116_0

16 Jan 12:24
Compare
Choose a tag to compare
Add runtime crypto routines for hashing and HMACing data from KV.

Due to hardware limitations these use HMAC and ECDSA keygen, respectively.