fix: embed attestation can lookup chalk keys in multiple paths #445
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CHANGELOG.md
if necessaryIssue
chalk was not picking up existing key in CI
for example https://github.com/zaproxy/zaproxy/actions/runs/11739273654/job/32703450631
Description
Previously embed provider only looked up keys in a single location which by default was current working directly.
This is not desirable in CI as placing additional files in PWD can have other side-effects.
As such setup-chalk-action was placing the generated key relative to chalk binary however chalk was not able to lookup that key.
Testing
Try loading existing key in CI