chore(release): 0.1.39 #39
matej21Annotations
5 errors and 1 warning
|
publish
Process completed with exit code 2.
|
|
publish:
tests/unit/editor/hybridBlocks.test.tsx#L151
Property 'testimonial' comes from an index signature, so it must be accessed with ['testimonial'].
|
|
publish:
tests/unit/editor/hybridBlocks.test.tsx#L151
'blocks.testimonial' is possibly 'undefined'.
|
|
publish:
tests/unit/editor/hybridBlocks.test.tsx#L147
Property 'testimonial' comes from an index signature, so it must be accessed with ['testimonial'].
|
|
publish:
tests/unit/editor/hybridBlocks.test.tsx#L146
Type '{ render: (props: RenderElementProps & { isVoid: boolean; }, ref: EntityAccessor<ContentReference, ContentReference, ComponentBrand, string, Record<...>> | null) => Element; isVoid?: boolean | undefined; staticRender?: ((ref: EntityAccessor<...>) => ReactNode) | undefined; }' is not assignable to type 'BlockDefinition<ContentReference, ContentReference, ComponentBrand, string, Record<string, object>>'.
|
|
publish
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 16th, 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/
|