Skip to content

Cleanup Rules for Packages Should Use "Last Updated" Time for Maven Snapshots #34382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dianaStr7 opened this issue May 6, 2025 · 0 comments
Labels
topic/packages type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@dianaStr7
Copy link
Contributor

Feature Description

Right now, Gitea uses the creation time of a package to determine when to delete it via cleanup rules. This works fine for most packages, but it doesn't quite fit how Maven snapshot versions are used. Snapshots often get updated frequently while keeping the same version label (like 1.0.0-SNAPSHOT). So even if a snapshot was created a while ago, it might still be actively used and updated.

That's why it makes more sense to base cleanup decisions on the last updated time instead of when it was first created - at least for snapshots. This way, actively used snapshots aren't deleted just because they were created a long time ago.

Proposed Solution:

  • Allow package cleanup rules to choose whether to use created_at or last_updated_at
  • For snapshot versions, it might even make sense to default to using last_updated_at

Screenshots

No response

@dianaStr7 dianaStr7 added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label May 6, 2025
@dianaStr7 dianaStr7 changed the title Cleanup Rules for Packages Should Use "Last Updated" Time for Snapshots Cleanup Rules for Packages Should Use "Last Updated" Time for Maven Snapshots May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/packages type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants