Compare commits

..

2 Commits

Author SHA1 Message Date
dependabot[bot]
1026f8604e
Merge 1f4e531cf091e39dea3bd401a4f777e30bbc9e83 into 1bd1e32a3bdc45362d1e726936510720a7c30a57 2024-12-09 21:11:15 +00:00
dependabot[bot]
1f4e531cf0
Bump actions/publish-immutable-action
Some checks failed
Code scanning - action / CodeQL-Build (push) Has been cancelled
Bumps the minor-actions-dependencies group with 1 update: [actions/publish-immutable-action](https://github.com/actions/publish-immutable-action).


Updates `actions/publish-immutable-action` from 0.0.3 to 0.0.4
- [Release notes](https://github.com/actions/publish-immutable-action/releases)
- [Commits](https://github.com/actions/publish-immutable-action/compare/0.0.3...v0.0.4)

---
updated-dependencies:
- dependency-name: actions/publish-immutable-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-actions-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-12-09 21:11:12 +00:00

View File

@ -102,7 +102,7 @@ The [GitHub Context](https://docs.github.com/en/actions/learn-github-actions/con
While setting paths for caching dependencies it is important to give correct path depending on the hosted runner you are using or whether the action is running in a container job. Assigning different `path` for save and restore will result in cache miss.
Below are GitHub hosted runner specific paths one should take care of when writing a workflow which saves/restores caches across OS.
Below are GiHub hosted runner specific paths one should take care of when writing a workflow which saves/restores caches across OS.
#### Ubuntu Paths