Skip to content
Back to pull request #4235

Alternative approach for findSchemaChanges #576

Sign in to view logs

Alternative approach for findSchemaChanges

Alternative approach for findSchemaChanges #576

Triggered via push October 14, 2024 17:06
@JoviDeCroockJoviDeCroock
pushed 4c059f6
find-schema-changes
Status Success
Total duration 2m 7s
Artifacts 3

push.yml

on: push
Matrix: ci / test
ci  /  Lint source files
1m 4s
ci / Lint source files
ci  /  Check for commonly ignored files
6s
ci / Check for commonly ignored files
ci  /  Check health of package-lock.json file
20s
ci / Check health of package-lock.json file
ci  /  Run integration tests
1m 28s
ci / Run integration tests
ci  /  Run fuzzing tests
36s
ci / Run fuzzing tests
ci  /  Run CodeQL security scan
1m 54s
ci / Run CodeQL security scan
ci  /  Build 'npmDist' artifact
35s
ci / Build 'npmDist' artifact
ci  /  Build 'denoDist' artifact
20s
ci / Build 'denoDist' artifact
ci  /  Build website
1m 4s
ci / Build website
Deploy to `deno` branch  /  deploy-artifact-as-branch
Deploy to `deno` branch / deploy-artifact-as-branch
Deploy to `npm` branch  /  deploy-artifact-as-branch
Deploy to `npm` branch / deploy-artifact-as-branch
Fit to window
Zoom out
Zoom in

Artifacts

Produced during runtime
Name Size
denoDist Expired
205 KB
npmDist Expired
449 KB
websiteDist Expired
2.31 MB