surrogate-key computation needs to use base ref instead of commit sha

[tripodsan]

The surrogate-key computation uses the context.content.sources, which specifies the entire, original url where the markdown content was fetched. for example:

https://raw.githubusercontent.com/tripodsan/hlxtest/bb8fc39dc3e01021bf1d30ac1ed4d0de04cbf5bc/index.md

The problem is, that in order to (soft) purge the fastly cache, when the index.md is modified, the bot doesn't know exactly which SHA was used to compute the .html.

the surrogate key should be computed using the original ref. e.g. master. suggest to include an additional parameter branch to the action.request.params.

the surrogate key will then be computed using:

https://raw.githubusercontent.com/${owner}/${repo}/${branch}${path}

@trieloff helix-dispatch also needs to include the new branch param.

[adobe-bot]

🎉 This issue has been resolved in version 4.0.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀