Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

on PR getting Error: Not Found #165

Open
ck1828 opened this issue Jan 30, 2023 · 4 comments
Open

on PR getting Error: Not Found #165

ck1828 opened this issue Jan 30, 2023 · 4 comments

Comments

@ck1828
Copy link

ck1828 commented Jan 30, 2023

When I use this action to bump and create tag
```

  • name: Bump version and push tag
    id: tag_version
    uses: mathieudutour/[email protected]
    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
@rbecheras
Copy link

It seems we had the same issue. Have you solved it?

@DameonSmith
Copy link

Any update on this for either of you?

@liamnv
Copy link

liamnv commented Apr 11, 2023

Any update?

@rbecheras
Copy link

rbecheras commented Apr 12, 2023

Hey, I succeeded in using it, but I missed coming back here to help.

If I remember well, this was due to the personal access token (PAT) setup.

In my case, I use a token owned by an internal bot acting as a GitHub user in my org.

This bot (the PAT owner) must have write/maintainer/admin permissions on your repo (depending on your GitHub repo settings)

Hoping it will help.

Could you confirm if it solved your issues?

That way, @mathieudutour you should be able to add this warning in the troubleshooting section in the readme, or even better, check for the PAT owner permissions before execution and display a more semantic error message if the permissions are not enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants