Bump @types/jasmine from 1.3.7 to 6.0.0 #9
lint-and-typecheck.yml
on: pull_request
lint-and-typecheck
56s
Annotations
10 errors and 1 warning
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L216
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L201
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L197
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L193
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L168
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L136
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L121
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L94
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L70
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck:
packages/bind/spec/asyncBindingBehaviors.ts#L45
Property 'Clock' does not exist on type 'typeof jasmine'. Did you mean 'clock'?
|
|
lint-and-typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|