github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-22 05:15:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Data retention settings for package registry #9388

New Issue
Closed
opened 2025-11-02 08:37:21 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 08:37:21 -06:00
Owner
Copy Link

Originally created by @fuero on GitHub (Aug 11, 2022).

Feature Description

The package registry feature should offer settings for data retention for package versions:

  • How long versions are kept,
  • how many versions are kept,
  • globally, per organization, per repo.

The goal is to allow to conserve space without having to manually delete packages.

If that's already possible, I've missed it in the docs - so please point it out to me :-)

Screenshots

No response

Originally created by @fuero on GitHub (Aug 11, 2022). ### Feature Description The package registry feature should offer settings for data retention for package versions: - How long versions are kept, - how many versions are kept, - globally, per organization, per repo. The goal is to allow to conserve space without having to manually delete packages. If that's already possible, I've missed it in the docs - so please point it out to me :-) ### Screenshots _No response_
GiteaMirror added the topic/packagestype/proposaltype/feature labels 2025-11-02 08:37:21 -06:00
GiteaMirror commented 2025-11-02 08:37:23 -06:00
Author
Owner
Copy Link

@hypervtechnics commented on GitHub (Aug 11, 2022):

And there should be an option using e.g. Regex or a semver parser to semantically select version to retain e.g. only last 5 prereleases

@hypervtechnics commented on GitHub (Aug 11, 2022): And there should be an option using e.g. Regex or a semver parser to semantically select version to retain e.g. only last 5 prereleases
GiteaMirror commented 2025-11-02 08:37:23 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Aug 11, 2022):

related #20514

@KN4CK3R commented on GitHub (Aug 11, 2022): related #20514
GiteaMirror commented 2025-11-02 08:37:23 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Nov 2, 2022):

Implemented this in #21658.

@KN4CK3R commented on GitHub (Nov 2, 2022): Implemented this in #21658.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/packages type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9388
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?