Limits/pricing for release artifact storage (in a project "release") for private repo?

[FelixSchwarz]

Select Topic Area

Question

Body

Suppose I have a private repo and we are using GitHub releases. Now we upload some release artifacts to a release. How are these artifacts billed?

• I guess attached a few files with like 100 MB each is not a problem?
• I assume github will bill us for disk space of these artifacts but I'm not sure how much? Do these files count against "Packages storage"?

I was not able to find something in the docs but probably I just used the wrong search terms so I'd be glad for pointers.

[DFelten]

I've got the same question. Are there any official information regarding the release artifacts of private repositories?

[JamesXNelson]

I'm looking for this answer too. /subbed/

I saw where LFS is $5 / 50GB storage+transfer.... but nowhere can I see prices for releases at all.

[rtrad89]

Same question here, are release artefacts counted towards package storage quotas?

[rtrad89]

Same question here, are release artefacts counted towards package storage quotas?

After some experiments, I think they are not considered artefacts. They are stored outside the shared storage and are not therefore exhausting the quota. Still, an official confirmation will be more watertight.

[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! 💬

[sevenate]

Our company is also considering to use GitHub Releases as a long term storage for artifact binaries, but without clear official statement somewhere on pricing if (or how) Releases are billed - preventing us from making a move.

[sevenate]

I did actually found this here:

Each file included in a release must be under 2 GiB. There is no limit on the total size of a release, nor bandwidth usage.

Which sounds great, but still surprised that it is not mentioned on the more approachable pricing page.

[BenjamenMeyer]

would be nice to know about retention period too. actions/upload-artifacts mentions and points to a repository setting about artifact retention (90 day max for public repos, 400 day for private); but I can't find anything about releases. Working on a public open source project and we're trying to determine what tools to use for our release process across multiple platforms.

[Colvin-Cowie-i2]

That is referring to Action Artifacts rather than Release Assets. Releases shouldn't expire.

[BenjamenMeyer]

That is referring to Action Artifacts rather than Release Assets. Releases shouldn't expire.

that's not obvious from the actions themselves

[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! 💬