How to Unpublish a Release?

[prembala1710]

Select Topic Area

Question

Body

Hey Guys,

I was working on a Github Action. There was a way to trigger Events based on the Release Event. It has a Sub Activity called unpublished. Can Someone Explain how to do a Unpublish?

[jge162]

@prembala1710 here are the steps

• Go to the GitHub repository that contains the release you want to unpublish.
• Click on the "Releases" tab.
• Find the release you want to unpublish and click on it.
• Click the "Edit" button at the top right of the release page.
• Scroll to the bottom of the page and click the "Delete release" button.
• Confirm that you want to delete the release by clicking the "Delete" button.

[hade]

@prembala1710, did you find out the answer to this? I first thought that a draft release would be "unpublished" but it dit not trigger the workflow.

[hade]

"unpublished" event is not listed as a trigger in the GitHub Actions documentation that I can see. It appears that only the "published", "created", and "deleted" events can trigger workflows in GitHub Actions.

@jge162, "unpublished" is indeed mentioned in the documentation. Please check again.

[jge162]

Yes it’s mentioned. I know. But it’s not a trigger.

[prembala1710]

@prembala1710, did you find out the answer to this? I first thought that a draft release would be "unpublished" but it dit not trigger the workflow.

Nope. As far as it went thorough the Documentation of the Github , There wasn't much of a Detailing expect the Page Events that Trigger a Github Workflow. So I Assume that either @jge162 's Perspective is the Right One or they are either yet to release the Feature of Unpublishing a Release.

[JasonPubC]

I am also looking into this feature - it is mentioned in the docs but has no trigger yet. I think you are right that this is not a feature yet.

I would expect the event "unpublished" can only occur after the published event has happened...

Deleting a release isn't always desirable, as you may want to keep a record of that release happening.

I would expect the following scenario:

• Publish release - triggers publish event
• New button to "Unpublish" the release is available - so you have the option to delete or unpublish
• Trigger the "unpublish" event so workflows can take advantage of it, and keep the release notes hidden/marked as a broken release
• New permissions to restrict who can unpublish would be helpful

In the workflows, I am sure they can decide whether they want to remove tags, deployments, or do any other kind of cleanup they want.

[YasinDehfuli]

its because of github terms for large files , The Maximum size of Repo is 5GB

You Can read this :
https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬