Skip to content
CI

Fix in-range? contract to allow "writing" empty u8vectors #4937

Sign in to view logs

Fix in-range? contract to allow "writing" empty u8vectors

Fix in-range? contract to allow "writing" empty u8vectors #4937

Triggered via pull request October 16, 2024 21:50
@drewcdrewc
synchronize #1275
bugfix-u8
Status Success
Total duration 31m 54s
Artifacts –

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (--enable-shared)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (--with-gambit=master, --enable-shared)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (--with-gambit=master)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/