Please check if the PR fulfills these requirements
[x] You have a descriptive and meaningful commit message.
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)
[x] You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the fix/ or feature/ prefixes. Good examples are: fix/signin-issue or feature/issue-templates.
[x] You have commented the code, particularly in hard-to-understand areas
What kind of change does this PR introduce? (Bug fix, new feature, docs update, ...)
Upgrade reference implementation pipeline version
How is it being tested (test Configuration)?
Clone the repo in ea new directory, follow the readme instructions to run the test sample, ensure results is consistant
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
param.yml file changes. this might break backward compatibility.
to mitigate the issue, example files are provided
Please check if the PR fulfills these requirements
[x] You have a descriptive and meaningful commit message.
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)
[x] You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the
fix/orfeature/prefixes. Good examples are:fix/signin-issueorfeature/issue-templates.[x] You have commented the code, particularly in hard-to-understand areas
What kind of change does this PR introduce? (Bug fix, new feature, docs update, ...) Upgrade reference implementation pipeline version
How is it being tested (test Configuration)?
Clone the repo in ea new directory, follow the readme instructions to run the test sample, ensure results is consistant
param.yml file changes. this might break backward compatibility. to mitigate the issue, example files are provided