feat(1739): schedule transaction implementation #2706
Triggered via pull request
March 31, 2026 15:25
mmyslblocky
mmyslblocky
opened
#1752
Status
Cancelled
Total duration
18s
Artifacts
–
flow-pull-request-formatting.yaml
on: pull_request_target
Title Check
11s
Annotations
3 errors and 1 warning
|
Title Check
Canceling since a higher priority waiting request for pr-formatting-PR Formatting-feat/1739-schedule-transaction-implementation exists
|
|
Title Check
No release type found in pull request title "Feat/1739 schedule transaction implementation". The title should match the commit message format as specified by https://www.conventionalcommits.org/. The functionalities can also be altered by the selected preset plugin (conventional-changelog-conventionalcommits).
Please use one of these recognized types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
|
|
PR Formatting
Canceling since a higher priority waiting request for pr-formatting-PR Formatting-feat/1739-schedule-transaction-implementation exists
|
|
Title Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@20cf305ff2072d973412fa9b1e3a4f227bda3c76. 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/
|