docs(RELEASE_MANAGEMENT): explain auto-merge for release PRs is a no-no #2528
ci.yaml
on: pull_request
build-dev
13s
compute_changed_packages
4s
ActionLint
/
Lint_GitHub_Actions
10s
DCI-Lint
32s
ghcr-besu-all-in-one
22s
ghcr-corda-all-in-one-flowdb
19s
ghcr-example-carbon-accounting
59s
ghcr-example-supply-chain-app
1m 2s
ghcr-fabric2-all-in-one
1m 52s
ghcr-keychain-vault-server
1m 35s
ghcr-quorum-all-in-one
40s
ghcr-quorum-multi-party-all-in-one
29s
yarn_lint
6m 2s
yarn_codegen
8m 30s
yarn_custom_checks
5m 33s
yarn_tools_validate_bundle_names
5m 22s
cactus-api-client
5m 49s
cactus-cmd-socketio-server
6m 5s
cactus-common
5m 46s
cactus-core
5m 28s
cactus-core-api
5m 35s
ce-carbon-accounting-backend
5m 55s
ce-carbon-accounting-business-logic-plugin
5m 31s
ce-carbon-accounting-frontend
5m 43s
ce-supply-chain-backend
25m 12s
ce-supply-chain-business-logic-plugin
6m 5s
ce-supply-chain-frontend
5m 16s
cp-consortium-manual
5m 37s
cp-htlc-coordinator-besu
7m 52s
cp-htlc-eth-besu
5m 45s
cp-htlc-eth-besu-erc20
5m 33s
cp-keychain-aws-sm
6m 42s
cp-keychain-azure-kv
5m 36s
cpk-google-sm
5m 42s
cpk-memory
5m 26s
cpk-memory-wasm
5m 41s
cpk-vault
6m 14s
cplc-go-ethereum-socketio
5m 12s
cplc-sawtooth
6m 42s
cplc-xdai
7m 18s
cpp-ethereum
7m 50s
cp-object-store-ipfs
6m 1s
cp-bungee-hermes
20m 56s
ct-api-client
6m 29s
ct-geth-ledger
6m 8s
ctp-consortium-manual
5m 59s
ctp-htlc-eth-besu
9m 49s
ctp-htlc-eth-besu-erc20
10m 17s
ctp-ledger-connector-ethereum
6m 21s
cactus-verifier-client
5m 40s
cactus-cmd-api-server
0s
cpl-connector-aries
0s
cpl-connector-besu
0s
cpl-connector-polkadot
0s
cpl-connector-corda
0s
cpl-connector-stellar
0s
plc-fabric-0
0s
plc-fabric-1
0s
plc-fabric-2
0s
plc-fabric-3
0s
plc-fabric-4
0s
plc-fabric-5
0s
plc-fabric-6
0s
plc-fabric-7
0s
plc-fabric-8
0s
plc-fabric-9
0s
plc-fabric-10
0s
plc-fabric-11
0s
plc-fabric-12
0s
cplc-iroha2
0s
cplc-ethereum
0s
cplc-quorum
0s
ct-cmd-api-server
0s
ctp-ledger-connector-besu
0s
ctp-ledger-connector-quorum
0s
cactus-test-tooling
0s
ghcr-cmd-api-server
0s
ghcr-connector-besu
0s
ghcr-connector-corda-server
0s
ghcr-connector-fabric
0s
ghcr-corda-all-in-one
0s
ghcr-corda-all-in-one-obligation
0s
ghcr-dev-container-vscode
0s
Annotations
1 error and 7 warnings
ghcr-corda-all-in-one-flowdb
Process completed with exit code 1.
|
compute_changed_packages
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: dorny/paths-filter@v2.11.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ActionLint / Lint_GitHub_Actions
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
DCI-Lint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
DCI-Lint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
DCI-Lint
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
yarn_codegen
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/github-script@v6.4.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
cp-bungee-hermes
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3.6.0, actions/checkout@v3.5.2, actions/cache@v3.3.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|