Releases: 51Degrees/pipeline-dotnet
Releases · 51Degrees/pipeline-dotnet
Version 4.3.15
- BUILD: Updated build images. Use image variables shared in common-ci.
- BUILD: Added project local shared-variables.yml as required.
Version 4.3.14
- BUILD: Added retry to NuGet restore steps in build pipelines. This works around the issue where Azure pipelines can sometimes not connect.
Version 4.3.13
- REORG: Getting property type for cloud engines no longer uses reflection, but allows inheriting class to override for more complex types.
Version 4.3.11
- BUG: Fix a bug that causes a crash when using the 51Degrees.core.js endpoint. - See #13
- TEST: Add automated tests to check that the vary header is populated as expected for various scenarios.
- BUG: The Pipeline.GetMetaDataForProperty method would throw an exception and log an error in certain scenarios. It should not be logging, because what to do with the error is up to the caller. - See #16
- OPTIM: The JavaScriptBuilder would keep checking for the Fetch and Promise properties on every request in some scenarios. - See #16
Version 4.3.9
- BUG: The web integration should not try to add IP address to the evidence if it is null.
- TEST: Add tests to verify WebRequestEvidenceService behaviour around client IP address.
- BUG: If a property name from cloud does not correspond with a property in code, then the CloudAspectEngineBase would fail to create the corresponding AspectPropertyMetaData. This will now succeed as long as the cloud property has a type that can be mapped to a c# type. If not, a clear exception will be thrown.
- TEST: Add tests for the above bug fix in CloudAspectEngineBase.
- FEAT: Add a 'SetDataUpdateUseUrlFormatter' cofiguration setting. This allows users to disable the formatter from a configuration file.
- REF: Updated reference to common-ci.
Version 4.3.7
Included Changes:
- FEAT: CloudAspectEngineBase implements process method which handles retrieval of json response from CloudRequestEngine.
- FEAT: Added support for Testing .NET APIs on Linux.
- FEAT: Version the library file when building packages.
Version 4.3.3
- FEAT: Errors from cloud service will now cause a 'CloudRequestException' to be thrown. This will include the HTTP status code and response header values.
Version 4.3.2
Included changes:
- REF: Update submodules references.
- CLEANUP: Remove JavaScript submodule
- BUG: Fix broken link to resource keys page in documentation.
- FEAT: Add some error handling to the BuildJson method in the JsonBuilderElement.
Version 4.3.1
Included changes:
- BUILD: Added 'submodule-trigger.yml' pipeline to support automated release process.
- BUILD: Added a step to 'build-and-test.yml' pipeline to auto complete a pull request to main as part of the automated release process.
- BUILD: Changed nightly build to just run tests, not create packages.
- FEAT: Update sequence error messages
- BUG: Cloud request engine now has a mechanism to set the Origin header.
- EXAMPLE: Add a new example that demonstrates how to configure usage sharing.
- FEAT: Calculate the share usage 'MaximumQueueSize' setting automatically. This simplifies configuration for the user.
- DOC: Improve the comments on the configuration methods for ShareUsageBuilder.
- TEST: Add a test to verify that the Pipeline.GetPropertyMetaData method will work in concurrent environments.
- BUG: Modify the Pipeline.GetMetaDataForProperty method to work correctly in concurrent environments.
- EXAMPLE: Update URL for custom cloud engine example.
Version 4.3.0
- FEAT: The
SetHeadersElement
can be used to convert values from all 'SetHeader*' properties into a dictionary that can be used to populate the HTTP response headers. This element is added automatically for web integration pipelines. - FEAT: When using web integration, the pipeline will now automatically set HTTP headers in the response based on the values of properties starting with 'SetHeader'
- REFACTOR: Combine the separate 'options' configuration classes for ASP.NET Core and ASP.NET into a single class. Add an option to flag the 'SetHeader' functionality on/off.
- BUG: Should only try and read from the 'Form' property on an HTTP request after checking if the content type is correct. This closes #5 .
- BUG: ASP.NET Framework integration was not reading form parameters. This has now been corrected.
- TEST: Add some tests to verify that the functionality to add form parameters to evidence in the
WebRequestEvidenceService
is functioning correctly. - TEST: Add a new
JsonBuilderElement
test to verify thejavascriptProperties
element in the JSON for properties with typeJavaScript
,AspectPropertyValue<JavaScript>
orIAspectPropertyValue<JavaScript>
. - TEST: Modify the
JsonBuilderElement
tests to verify that the delayed evidence functionality works correctly is the property type isJavaScript
,AspectPropertyValue<JavaScript>
orIAspectPropertyValue<JavaScript>
. - BUG: Correct a bug that stopped properties from being included in the
javascriptProperties
list if they had typeAspectPropertyValue<JavaScript>
. - BUG:
JsonBuilderElement
was not correctly checkingJavaScript
types when getting delayed execution properties. This has now been corrected. Also moved the type check to a static utility class. - DOC: Commented the
UseFiftyOne
extension method to make it clear that it must be called before anyExceptionHandlerExtensions
methods. This closes #3 - BUILD: Use common-ci template.