mathieudutour / mathieudutour/github-tag-action

on PR getting Error: Not Found

Open
#165 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
733
Forks
227
PR merge metrics
No merged PRs in 30d

Description

When I use this action to bump and create tag
```
- name: Bump version and push tag
id: tag_version
uses: mathieudutour/github-tag-action@v5.6
with:
github_token:
```
It creates a new version but at the end throws NOT FOUND error
```
```
New version is 1.0.2.
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
New tag after applying prefix is v1.0.2.
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Changelog is ### [1.0.2](https://github.com/repo-name/compare/v1.0.1...v1.0.2) (2023-01-[30](https://github.com/repo-namee/actions/runs/4045200206/jobs/6956352181#step:4:31))
.
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Error: Not Found
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided workflow step and its action output, then trace where the successful version and tag creation is followed by the final “Error: Not Found.” Reproduce the run with the shown configuration and confirm that the completed behavior no longer ends in that error while the version, tag, and changelog outputs remain correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github-actions
Domain
ci-cd, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.