You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
We have identified a potential issue with the management of webhooks for a repository. Upon investigation on Zenodo, we discovered that the repository currently has two active webhooks directed to Zenodo: one created in 2018 and another in 2024.
Problem
Whenever a new release is received, it consistently utilizes the older webhook, which has invalid credentials. Consequently, the releases fail consistently due to this mismatch.
We
Objective
We aim to investigate whether this occurrence is consistent or if it was a one-time incident.
Steps to Reproduce
Have a repository jointly owned by two users (user A and user B).
Enable the repository with user A on Zenodo.
Verify the webhook created on Github.
Disable the repository.
Enable the repository with user B on Zenodo.
Verify the webhook created on Github.
Expected Outcome
If there are indeed two webhooks present in the repository, it indicates an issue with the cleanup process of webhooks.
The text was updated successfully, but these errors were encountered:
Description
We have identified a potential issue with the management of webhooks for a repository. Upon investigation on Zenodo, we discovered that the repository currently has two active webhooks directed to Zenodo: one created in 2018 and another in 2024.
Problem
Whenever a new release is received, it consistently utilizes the older webhook, which has invalid credentials. Consequently, the releases fail consistently due to this mismatch.
We
Objective
We aim to investigate whether this occurrence is consistent or if it was a one-time incident.
Steps to Reproduce
Expected Outcome
If there are indeed two webhooks present in the repository, it indicates an issue with the cleanup process of webhooks.
The text was updated successfully, but these errors were encountered: