How do I make new_tag available locally?

Nobody has claimed this yet.

Given this workflow:

```yaml
name: release
on:
push:
branches:
main
paths-ignore:
- 'package.json'
- 'CHANGELOG.md'

jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Check out code
uses: actions/checkout@v2
with:
fetch-depth: 0

- run: git tag -l

- name: Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v6.0
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
create_annotated_tag: true

- run: git tag -l
```

Both invocations of `git tag -l` show the same list of tags. Downstream steps like `ncipollo/release-action` are aware of the tag that this action creates, but I have a step in a java project that makes decisions based on tags present locally, and it's failing to find `new_tag`.

Is this expected behavior? I am wildly confused as to how this action applies its new tag :(

Start with the workflow in the issue, especially the two git tag -l steps, actions/checkout@v2, and mathieudutour/github-tag-action@v6.0. Compare the locally visible tags with the tag observed by ncipollo/release-action and determine whether the Java step can access new_tag; done means the expected tag is available locally or the behavior is clearly documented.

Written by the indexing model from the issue text.