setup-node: can NOT find cache

Description: I created branch node-cache-3 from branch node-cache. It means the branch node-cache-3 has the base branch node-cache, doesn’t it? In github docs, a branch can access to caches if its base branch creates caches.

A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually main). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch feature-b has the base branch feature-a, a workflow triggered on feature-b would have access to caches created in the default branch (main), feature-a, and feature-b.

link: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache

The branch node-cache-3 can NOT access to caches even if node-cache creates its caches in my repository.

link: https://github.com/guppy0356/gh-actions/runs/7296326981?check_suite_focus=true link: https://github.com/guppy0356/gh-actions/runs/7296402979?check_suite_focus=true

Action version: Specify the action version

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

I can’t understand runner type is.

Tools version:

yarn 1.22.19 node v16.15.1

Repro steps:

    - name: Use Node.js
      uses: actions/setup-node@v3
      with:
        node-version: 18
        cache: 'yarn'

Expected behavior: The branch node-cache-3 can access to caches created in the its base branch (node-cache).

Actual behavior: The branch node-cache-3 can NOT access to caches created in the its base branch (node-cache).

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (5 by maintainers)

Commits related to this issue

Most upvoted comments

@vsafonkin

no, no, no. please don’t close this. The caches created in base branch has NOT been accessible.