CCM-14238: Status Update For Records With Id "Test" (#450) #3637
francisco-videira-nhscicd-1-pull-request.yaml
on: push
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
17s
Commit stage
/
Check file format
12s
Commit stage
/
Check Markdown format
8s
Commit stage
/
Check English usage
9s
Commit stage
/
Check TODO usage
5s
Commit stage
/
Trivy Package Scan
18s
Commit stage
/
Count lines of code
10s
Commit stage
/
Scan dependencies
45s
Commit stage
/
Check for changes to event schema package compared to main branch
5s
Commit stage
/
Check event schema version has been updated
Commit stage
/
Check for event schemas package version change
Commit stage
/
Run terraform-docs
0s
Commit stage
/
Lint Terraform
0s
Commit stage
/
Trivy IaC Scan
0s
Test stage
/
Check generated dependencies
1m 13s
Test stage
/
Pact tests
1m 20s
Test stage
/
Linting
3m 21s
Test stage
/
Typecheck
1m 58s
Test stage
/
Test coverage
6s
Test stage
/
Perform static analysis
1m 3s
Matrix: Build stage / artefact-oas-spec
Acceptance stage
/
Run Acceptance Tests
5m 51s
Acceptance stage
/
Run End-to-End Tests
4s
Publish stage
/
Publish npm packages to npm.pkg.github.com
16s
Publish stage
/
Publish nuget packages to nuget.pkg.github.com
8s
Matrix: Publish stage / publish-oas-specs
Publish stage
/
Success notification
5s
Annotations
57 warnings
|
Commit stage / Check for changes to event schema package compared to main branch
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 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/
|
|
Commit stage / Trivy Package Scan
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 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/
|
|
Test stage / Check generated dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Pact tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/validation.ts#L67
Generic Object Injection Sink
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/validation.ts#L41
Unsafe Regular Expression
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/common-ids.ts#L5
Prefer default export on a file with single export
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/__tests__/validation.test.ts#L74
Test has no assertions
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/post-mi.ts#L5
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMIOperation`. Check if you meant to write `import postMI from '../services/mi-operations'` instead
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/utils/test-utils.ts#L3
Prefer default export on a file with single export
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/post-mi.test.ts#L7
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMiOperation`. Check if you meant to write `import postMI from '../../services/mi-operations'` instead
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/amendment-event-transformer.test.ts#L123
Generic Object Injection Sink
|
|
Test stage / Linting:
internal/helpers/src/id-ref.ts#L54
Variable Assigned to Object Injection Sink
|
|
Test stage / Linting:
internal/datastore/src/letter-repository.ts#L77
Variable Assigned to Object Injection Sink
|
|
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Build stage / Build Docs
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/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, ruby/setup-ruby@v1.180.1. 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/
|
|
Build stage / Build Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0hgm8aQAAAACtWtOHXhAeTIrKNA3c8fYNQ0hJMzBFREdFMDEyMQBFZGdl
|
|
Build stage / Build Docs
Failed to restore: Cache service responded with 400
|
|
Build stage / Build OAS spec (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build OAS spec for sandbox
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build OAS spec (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build OAS spec (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build OAS spec (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build OAS spec (internal-dev-pr)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build stage / Build SDKs
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/upload-artifact@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/
|
|
Build stage / Build proxies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
|
|
Publish stage / Publish packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-release@v1, actions/upload-release-asset@v1. 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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish packages
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/
|
|
Publish stage / Publish OAS spec (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@v1. 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/
|
|
Publish stage / Publish OAS spec (prod)
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/
|
|
Publish stage / Publish OAS spec (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@v1. 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/
|
|
Publish stage / Publish OAS spec (ref)
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/
|
|
Publish stage / Publish OAS spec (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@v1. 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/
|
|
Publish stage / Publish OAS spec (internal-dev)
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/
|
|
Publish stage / Publish OAS spec (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@v1. 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/
|
|
Publish stage / Publish OAS spec (int)
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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
api-oas-specification-int-1.1.5-20260319.142823+ae8ab44
|
20.9 KB |
sha256:7c3b283c797949f92c54da8510951947c46022d32c2f67a9bb39d3ad0337d056
|
|
|
api-oas-specification-internal-dev-1.1.5-20260319.142823+ae8ab44
|
20.9 KB |
sha256:41bc1d343f9726295cac3567f386b4c438efe8e35442be284985c476ca3a8eed
|
|
|
api-oas-specification-internal-dev-pr-1.1.5-20260319.142823+ae8ab44
|
20.7 KB |
sha256:c21708a3286dd048d55696e0d728cdea48fce92a0a6a9738670226f9054d4ad1
|
|
|
api-oas-specification-internal-dev-sandbox-1.1.5-20260319.142823+ae8ab44
|
20.9 KB |
sha256:aebbe0208e9bfe805bb6b1a0a23e7c498f9b4faf5db984b55e49afb9e2a51e63
|
|
|
api-oas-specification-prod-1.1.5-20260319.142823+ae8ab44
|
20.9 KB |
sha256:76e6838dbdb1c4cac10acc87ff081d2867d729502d14da7588ebdd1c0e78967b
|
|
|
api-oas-specification-ref-1.1.5-20260319.142823+ae8ab44
|
20.9 KB |
sha256:a28f3e684de4827ecbf8429df84242ea31bd027832f5d112843d0934d9c7e9cb
|
|
|
code-coverage-report
|
4.18 KB |
sha256:41efa53f43683466cd770f9473057f228f3f67e186c45b3f42a99fd9c7694d2e
|
|
|
internal-dev-sandbox-build-output
|
20.9 KB |
sha256:d5071a59a47e8bdf67dce6b740e8b3ce74c1a04ea3feb9e3f574b74a047391fd
|
|
|
jekyll-docs-1.1.5-20260319.142823+ae8ab44
Expired
|
1.4 MB |
sha256:bf00fe6bceb40d2a3cc2fdda00dd4b7b9b7eae62327cc59fa27cc89535def2ed
|
|
|
lines-of-code-report.json.zip
Expired
|
963 Bytes |
sha256:a727e3e9630b539348d39c8d17ee4bc90ace9fd736fc2694b7a39bf5d86cdfd8
|
|
|
sbom-repository-report.json.zip
Expired
|
153 KB |
sha256:18f24aa6328a0ad5f7fade3df3c9fd915c6c09aea97cc7bd5c25850331b2367f
|
|
|
sdk-csharp-1.1.5-20260319.142823+ae8ab44
|
1020 KB |
sha256:cba2e54df3ba6e9768f2fcebdccb149a2f15894d6a3de1faa478ab8df08856f0
|
|
|
sdk-html-1.1.5-20260319.142823+ae8ab44
|
8.54 KB |
sha256:9c63c69ebef04804613fe3fec867020d826ce0ad32dabb67b1dc5c499099aa26
|
|
|
sdk-html-docs-1.1.5-20260319.142823+ae8ab44
Expired
|
9.29 KB |
sha256:c002fa22d1bbcfd18a77eace17ac666c8f3eb9c6d39bf97003285d7c5bb1f340
|
|
|
sdk-python-1.1.5-20260319.142823+ae8ab44
|
223 KB |
sha256:354fcc89725bf46f331259d34f7dd63e6b3ef09d2a2bcdddadbd45faae9c7637
|
|
|
sdk-swagger-1.1.5-20260319.142823+ae8ab44
|
1.09 MB |
sha256:e995f85e3fd8ed520d93f81da3e6eb492db321a366bfbda272db6f3a065e756c
|
|
|
sdk-swagger-docs-1.1.5-20260319.142823+ae8ab44
Expired
|
1.09 MB |
sha256:e67871d40e5fce97c7233f765f312d5b5e03a94272044c09849ebc470fbd9433
|
|
|
sdk-ts-1.1.5-20260319.142823+ae8ab44
|
98.8 KB |
sha256:4159119c832e17dc04bf21eb886e192e98b45c4b1fe2e2b687571fc61a243247
|
|
|
unit-tests
|
803 KB |
sha256:4c8d7f07e00d94c21c44f67e4bf7bc294d873315473fd2441e9b8c0283e313d0
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
3.37 KB |
sha256:bb04bde57af04604a65e138004f7a5d35e790ed2cd527c6225913f9c7af01bff
|
|