Skip to content

Zenodo intergration not automatically working #43

@RayStick

Description

@RayStick

Expected Behavior

On a new release, the zenodo page is meant to update via the GH Action / Web Hook

Instead of the default info, the GitHub API should be reading the .zenodo.json file at the root of the GH repo to extract the metadata

Screenshot 2024-12-12 at 16 00 10

Actual Behavior

The zenodo page did not update after we changed the .zenodo.json file (see this PR: #33).

Zenodo has the last release at 0.5.1 where GH has it as 0.8.1

Solution tried and failed ...

  • Changed the webhook to trigger on push and new release
  • Ran these commands
    git commit --allow-empty -m "Trigger new release"
    git push origin master
  • Ooops SORRY I did not mean to trigger a new GH release on GH, I meant to just trigger a Zenodo release via an empty commit push
  • Zenodo page still at 0.5.1 =(
  • Got this error on the webhook: Last delivery was not successful. Invalid HTTP Response: 409.
  • Change webhook back to only trigger on new release (not any push) as it was before

Checked/Validated ...

  • I looked at guides online, and used JSON online validators and I think the JSON file itself is not the problem

Possible solution

  • Check Zenodo configuration (@smoia can you do this? or add me to the Zenodo account if you like)
    • check the "linked repositories" settings on the Zenodo account , that is is properly configured to receive webhooks from GitHub
    • ensure that the access token is still valid and has the necessary permissions.
  • Talk to the developers - Stefano said "Do you want to try to contact them [zenodo] again? that'd help. Alternatively, I saw that they are now working with CFF files, if you want to give it a try?"

❗ might be good to test things in this repo: https://github.com/physiopy/physiopy-test-workflows

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingHelp wantedExtra attention is needed

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions