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

Error after "Warning: No registry pull request was found for this version" #258

Closed
Jutho opened this issue Feb 24, 2023 · 5 comments · Fixed by #264
Closed

Error after "Warning: No registry pull request was found for this version" #258

Jutho opened this issue Feb 24, 2023 · 5 comments · Fixed by #264

Comments

@Jutho
Copy link

Jutho commented Feb 24, 2023

After registering a new package ( https://github.com/Jutho/StridedViews.jl ) it seems TagBot is not able to create the tag, and the action prints out the following warning:

Warning: No registry pull request was found for this version
Error: TagBot experienced an unexpected internal failure

See https://github.com/Jutho/StridedViews.jl/actions/runs/4260560015/jobs/7413862625#step:3:44

TagBot.yml file was created with the latest version of PkgTemplates.jl .

@rafaelbailo
Copy link

I've just had the same issue with https://github.com/rafaelbailo/Consensus.jl, having also used PkgTemplates.jl to configure TagBot.

@RexWzh
Copy link

RexWzh commented Mar 29, 2023

I get the same error just now.

@LudwigBoess
Copy link

I also get this error. I updated my TagBot workflow file to the latest version given in the README and also set up new SSH keys, just to be sure, but neither solved the problem

@junyuan-chen
Copy link

junyuan-chen commented Apr 1, 2023

Same here. Rerun the workflow doesn't help.

The same error shows up for both new packages and existing packages.

Here is the log:

Did not find registry PR
Processing version v0.1.0 (1fd3ed4e3d60f84cd96d0fce9d177949079a1e29)
Generating changelog for version v0.1.0 (1fd3ed4e3d60f84cd96d0fce9d177949079a1e29)
Warning: No registry pull request was found for this version
Creating release v0.1.0 at 1fd3ed4e3d60f84cd96d0fce9d177949079a1e29
Error: TagBot experienced an unexpected internal failure
Traceback (most recent call last):
  File "/root/tagbot/action/__main__.py", line 94, in <module>
    repo.create_release(version, sha)
  File "/root/tagbot/action/repo.py", line 5[45](https://github.com/junyuan-chen/NonlinearSystems.jl/actions/runs/4581529946/jobs/8091119101#step:3:46), in create_release
    self._repo.create_git_release(
  File "/usr/local/lib/python3.8/site-packages/github/Repository.py", line 1059, in create_git_release
    headers, data = self._requester.requestJsonAndCheck(
  File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 315, in requestJsonAndCheck
    return self.__check(
  File "/usr/local/lib/python3.8/site-packages/github/Requester.py", line 340, in __check
    raise self.__createException(status, responseHeaders, output)
github.GithubException.GithubException: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/releases/releases#create-a-release"}

Response (200): {
  "status": "Submitted error report"
}

navidcy referenced this issue in OceanBioME/OceanBioME.jl Jun 24, 2023
Update Oceananigans/KernelAbstractions versions
@navidcy
Copy link

navidcy commented Jun 28, 2023

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

Successfully merging a pull request may close this issue.

6 participants