Skip to content
Publish to npm

Allow define projection fields in read model queries (#1481) #79

Sign in to view logs

Allow define projection fields in read model queries (#1481)

Allow define projection fields in read model queries (#1481) #79

Triggered via push May 30, 2024 15:06
@MarcAstr0MarcAstr0
pushed f747847
main
Status Success
Total duration 53m 5s
Artifacts 1

wf_publish-npm.yml

on: push
Ensuring integration tests pass before publishing  /  ...  /  prepare-integration-tests
1m 18s
Ensuring integration tests pass before publishing / prepare-integration-tests / prepare-integration-tests
Ensuring integration tests pass before publishing  /  notify-start
2s
Ensuring integration tests pass before publishing / notify-start
Ensuring integration tests pass before publishing  /  ...  /  Azure Deploy
13m 11s
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Deploy
Ensuring integration tests pass before publishing  /  ...  /  CLI Integration Tests
3m 11s
Ensuring integration tests pass before publishing / cli-integration-tests / CLI Integration Tests
Ensuring integration tests pass before publishing  /  ...  /  Local Provider Integration Tests
1m 2s
Ensuring integration tests pass before publishing / local-integration-tests / Local Provider Integration Tests
Matrix: integration-tests / azure-integration-tests / azure-integration-tests
Ensuring integration tests pass before publishing  /  ...  /  Azure Nuke
20m 42s
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Nuke
Ensuring integration tests pass before publishing  /  notify-end-success
0s
Ensuring integration tests pass before publishing / notify-end-success
Ensuring integration tests pass before publishing  /  notify-end-failure
0s
Ensuring integration tests pass before publishing / notify-end-failure
Publish to npm
2m 45s
Publish to npm
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Ensuring integration tests pass before publishing / prepare-integration-tests / prepare-integration-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / local-integration-tests / Local Provider Integration Tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / cli-integration-tests / CLI Integration Tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3, azure/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Ensuring integration tests pass before publishing / azure-integration-tests / azure-integration-tests (azure-func)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3, azure/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / azure-integration-tests / azure-integration-tests (azure-func)
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Ensuring integration tests pass before publishing / azure-integration-tests / azure-integration-tests (azure-end-to-end)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3, azure/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / azure-integration-tests / azure-integration-tests (azure-end-to-end)
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Nuke
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3, azure/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Ensuring integration tests pass before publishing / azure-integration-tests / Azure Nuke
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
integration-test-dependencies-f747847ae1830f7ee373d6128d316e522172ca05 Expired
591 KB