Skip to content
CI

Switch away from using npm for metro #5203

Sign in to view logs

Switch away from using npm for metro

Switch away from using npm for metro #5203

Triggered via pull request November 5, 2024 16:47
@anthonyshullanthonyshull
synchronize #2212
ags/use-non-npm-metro
Status Success
Total duration 7m 0s
Artifacts 1

tests.yml

on: pull_request
file_changes
4s
file_changes
Build application and assets
5m 43s
Build application and assets
Build Docker image
5m 25s
Build Docker image
Linting / TypeScript
1m 31s
Linting / TypeScript
Linting / JavaScript
1m 21s
Linting / JavaScript
Linting / CSS
1m 27s
Linting / CSS
Linting / Elixir
3m 56s
Linting / Elixir
Unit tests / JavaScript / Mocha
1m 28s
Unit tests / JavaScript / Mocha
Unit tests / JavaScript & TypeScript / Jest
3m 6s
Unit tests / JavaScript & TypeScript / Jest
Type checks / Elixir
4m 17s
Type checks / Elixir
Type checks / TypeScript
1m 31s
Type checks / TypeScript
Formatting / Elixir
3m 44s
Formatting / Elixir
Formatting / JavaScript & TypeScript
1m 23s
Formatting / JavaScript & TypeScript
Unit tests / Elixir / mix coveralls.html
59s
Unit tests / Elixir / mix coveralls.html
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Type checks / Elixir
The following actions use a deprecated Node.js version and will be forced to run on node20: mbta/actions/dialyzer@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
Elixir test coverage report
710 KB