Release/v5.0.0 #3
PR-CI.yml
on: pull_request
Annotations
23 warnings
|
Build-Release
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-dotnet@v3, actions/upload-artifact@v4, gittools/actions/gitversion/execute@v0.9.7, gittools/actions/gitversion/setup@v0.9.7. 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-Release:
src/DomainEvents/IEventMiddleware.cs#L44
Missing XML comment for publicly visible type or member 'EventContext.Event'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L63
Missing XML comment for publicly visible type or member 'LoggingMiddleware.OnHandledAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L57
Missing XML comment for publicly visible type or member 'LoggingMiddleware.OnHandlingAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L51
Missing XML comment for publicly visible type or member 'LoggingMiddleware.OnDispatchedAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L45
Missing XML comment for publicly visible type or member 'LoggingMiddleware.OnDispatchingAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L40
Missing XML comment for publicly visible type or member 'LoggingMiddleware.LoggingMiddleware(ILogger<LoggingMiddleware>)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L27
Missing XML comment for publicly visible type or member 'EventMiddlewareBase.OnHandledAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L22
Missing XML comment for publicly visible type or member 'EventMiddlewareBase.OnHandlingAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L17
Missing XML comment for publicly visible type or member 'EventMiddlewareBase.OnDispatchedAsync(EventContext)'
|
|
Build-Release:
src/DomainEvents/EventMiddlewareBase.cs#L12
Missing XML comment for publicly visible type or member 'EventMiddlewareBase.OnDispatchingAsync(EventContext)'
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Build-Release
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/
|
|
Package-Artifacts
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/
|
|
Run-Lint
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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-artifact
Expired
|
5.04 MB |
sha256:9410d0dc9536151a4bffbe552fcdc6caacbf1c030643aa7df4e1a468a9b72c54
|
|