Work around cache module modifying input paths

[Bertg]

An issue in action/toolkit modifies the inputPath values passed to cache function. These changes work around this issue.

For more details see: actions/toolkit#1378

This resolves #175

[bahmutov]

very interesting, merging now

[github-actions]

🎉 This PR is included in version 1.8.33 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[oleksandr-danylchenko]

@Bertg, thank you so much!

[oleksandr-danylchenko]

Are there any dates on when the version bump in the GitHub Actions marketplace is planned for?
Seems like it's still using the 1.6.0 version, instead of the latest 1.8.33

[bahmutov]

@oleksandr-danylchenko the version displayed on GitHub Actions marketplace does not matter, you still pick the version you want to use. I should find out if there is an automatic way to update the marketplace version

[oleksandr-danylchenko]

Thanks 👌🏻
I manually picked the 1.8.33 version in the action. Just wondering about the marketplace to be able to use the latest version automatically just with @1

[Bertg]

@oleksandr-danylchenko We use the @1 notion in our workflows. And we are seeing cache hits again. So I'm fairly certain it just works, and there is a disconnect between the marketplace displayed version, and the actual version resolution in the GitHub actions.

[Bertg]

@bahmutov If you still are looking into the issue, as to why the version in marketplace is lagging, here are the docs: https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace

It may have something to do with accepting the "GitHub Marketplace Developer Agreement", which is something that is new to me, and maybe to you as well?