Skip to content

1.0.0-rc5

1.0.0-rc5 #435

  • lz-test requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by ronaldo-macapobre in Deploy API #435

Triggered via release March 10, 2026 23:32
Status Waiting
Total duration
Artifacts 1
  • lz-test requires an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by ronaldo-macapobre in Deploy API #435

publish-api.yml

on: release
Matrix: Build, Create and Push Image
Deploy to TEST
Deploy to TEST
lz-test waiting for review
Deploy to PROD
Deploy to PROD
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
ronaldo-macapobre
requested review
lz-test -

Annotations

1 error and 20 warnings
Build, Create and Push Image (10, 0)
Process completed with exit code 2.
Build, Create and Push Image (10, 0)
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0)
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0)
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0)
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0)
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0)
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0)
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0)
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0)
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0)
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L6
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L5
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): pcss-client/Clients/PersonServicesClient.cs#L153
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderActionDto.cs#L38
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderTerm.cs#L8
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L6
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): api/Models/Dars/TranscriptSearchRequest.cs#L5
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build, Create and Push Image (10, 0): pcss-client/Clients/PersonServicesClient.cs#L153
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderActionDto.cs#L38
Non-nullable property 'OrderTerms' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build, Create and Push Image (10, 0): cso-client/Models/Order/OrderTerm.cs#L8
Non-nullable property 'TermTxt' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Artifacts

Produced during runtime
Name Size Digest
bcgov~jasper~CMDJBV.dockerbuild
62.7 KB
sha256:95d96101811594034c324af6cd62a4c7f898b0bd96b1622993784340fcd689ab