TagBot: Manual intervention needed for releases

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
git, github-actions
Domain
ci-cd, release

Research direction

Start with the TagBot run logs and the .github/workflows/ci.yml permission error. Use the listed commit hashes and release commands to create and push tags for v0.6.8, v0.7.0, and v0.9.0, then verify that GitHub releases exist for all three versions and mark the checklist complete.

Written by the indexing model from the issue text.

Description

tagbot-manual

TagBot could not automatically create releases for the following versions. This may be because:

  • The commits modify workflow files (.github/workflows/), which GITHUB_TOKEN cannot operate on
  • The tag already exists but the release failed to be created
  • A network or API error occurred

Versions needing manual release

  • v0.6.8 at commit 815bf2a5
  • v0.7.0 at commit 97a42ed9
  • v0.9.0 at commit be60ba05

How to fix

Run these commands locally:

git tag -a v0.6.8 815bf2a50280e406d571c23a872e3b16cbc2fc93 -m 'v0.6.8' && git push origin v0.6.8 && gh release create v0.6.8 --generate-notes
git tag -a v0.7.0 97a42ed985aa7418ab473f0b320dd068bfca616f -m 'v0.7.0' && git push origin v0.7.0 && gh release create v0.7.0 --generate-notes
git tag -a v0.9.0 be60ba057ff6bae3be2ffbce314bb40391360439 -m 'v0.9.0' && git push origin v0.9.0 && gh release create v0.9.0 --generate-notes

Or create releases manually via the GitHub UI.

Prevent this in the future

If this is due to workflow file changes, avoid modifying them in the same commit as version bumps, or use a Personal Access Token with workflow scope.

See TagBot troubleshooting for details.


This issue was automatically created by TagBot. (Run logs)

Dominant language
Julia
Stars
71
Forks
12
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from JuliaGraphs/MetaGraphs.jl

All issues in JuliaGraphs/MetaGraphs.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.