[ty] Fix notifications about watched changes for entities outside any… #573
ci.yaml
on: push
Determine changes
21s
cargo clippy
2m 17s
cargo test (linux)
14m 30s
cargo test (wasm)
4m 2s
cargo build (msrv)
3m 16s
test scripts
1m 9s
cargo test (linux, release)
0s
cargo fuzz build
4m 48s
fuzz parser
0s
ecosystem
0s
Fuzz for new ty panics
cargo shear
23s
ty completion evaluation
3m 2s
formatter instabilities and black similarity
3m 6s
test ruff-lsp
2m 32s
check playground
0s
benchmarks instrumented (ruff)
0s
Matrix: cargo-test-other
Matrix: benchmarks-instrumented-ty-run
Matrix: benchmarks-walltime-run
all required checks passed
3s
Annotations
2 errors and 2 warnings
|
cargo test (windows-latest)
The job has exceeded the maximum execution time of 20m0s
|
|
cargo test (windows-latest)
The operation was canceled.
|
|
cargo build (msrv)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SebRollen/toml-action@b1b3628f55fc3a28208d4203ada8b737e9687876. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo test (wasm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jetli/wasm-pack-action@0d096b08b4e5a7de8c28de67e11e945404e9eefa. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|