Create/update the new v2 tag locally, where the new v2 tag will point to the
release that you created in the previous step.
Make sure to change v2.2.0 to the actual value for the tag that you just
created in the previous step.
The -f flag forcibly overwrites the old
v2 tag (if it exists).
git tag -f v2 v2.2.0
Step 3: Now you need to push the tags:
# Regular-push the new `v2.2.0` tag:
git push origin tag v2.2.0
# Force-push the new v2 tag:
git push origin tag v2 --force
</code></pre>
<h2>Part 2: Create the GitHub Release</h2>
<p>Go to the <a href="https://github.com/julia-actions/cache/releases">Releases</a> section of this repo and create a new release (using the GitHub web interface).</p>
<p>For the "choose a tag" drop-down field, select the <code>v2.2.0</code> tag that you created and pushed in Part 1 of this guide.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/julia-actions/cache/commit/580d2b69d895343992af2cbad49c32a0149c2cde"><code>580d2b6</code></a> Fix issues with custom cache eviction (<a href="https://redirect.github.com/julia-actions/cache/issues/135">#135</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/e00c08a89a5b3dd353aae2f6d89c28a2d8bebab7"><code>e00c08a</code></a> README: document that Bash is required (<a href="https://redirect.github.com/julia-actions/cache/issues/132">#132</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/bb4225b87551c49ade2f5446fd0d23dceff5c131"><code>bb4225b</code></a> Devdocs: document the process for making a new release of this action (<a href="https://redirect.github.com/julia-actions/cache/issues/128">#128</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/8dfc57d68c2b66c144e72552a6c4797d4d571353"><code>8dfc57d</code></a> Bump actions/checkout from 4.1.4 to 4.1.6 (<a href="https://redirect.github.com/julia-actions/cache/issues/133">#133</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/3190fc83dbc582bbf8ccc2b5364f04864818d842"><code>3190fc8</code></a> Fix typo in <code>cache-name</code> note (<a href="https://redirect.github.com/julia-actions/cache/issues/130">#130</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/2185d31b1264155556c86bcf2539c7738fea65b0"><code>2185d31</code></a> Update README to recommend <code>julia-actions/cache@v2</code> (instead of <code>@v1</code>) (<a href="https://redirect.github.com/julia-actions/cache/issues/129">#129</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/d48542bb7b6239a9391789f01d21a6bdde9ad5df"><code>d48542b</code></a> Bump actions/cache from 3.3.3 to 4.0.2 (<a href="https://redirect.github.com/julia-actions/cache/issues/123">#123</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/caa655642cf9556f51525db05b49b33ace31b697"><code>caa6556</code></a> Bump pyTooling/Actions from 1.0.1 to 1.0.5 (<a href="https://redirect.github.com/julia-actions/cache/issues/127">#127</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/1c20782198d65b2708fdf6ba3da29473f74d5d47"><code>1c20782</code></a> Bump actions/checkout from 4.1.2 to 4.1.4 (<a href="https://redirect.github.com/julia-actions/cache/issues/126">#126</a>)</li>
<li><a href="https://github.com/julia-actions/cache/commit/4b23ab708f8ab9e305e7985858593260f3b31bf1"><code>4b23ab7</code></a> update setup-julia to v2 in readme (<a href="https://redirect.github.com/julia-actions/cache/issues/124">#124</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/julia-actions/cache/compare/v1...v2">compare view</a></li>
</ul>
</details>
<br />
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=julia-actions/cache&package-manager=github_actions&previous-version=1&new-version=2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps julia-actions/cache from 1 to 2.
Release notes
Sourced from julia-actions/cache's releases.
... (truncated)
Changelog
Sourced from julia-actions/cache's changelog.