Repository navigation
feat: add noncurrent lifecycle executor - #1687
Merged
Merged
Conversation
Coverage Report for CI Build 42856954115Coverage increased (+0.1%) to 87.603%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
TylerHillery
approved these changes
Nov 10, 2026
Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>
ferhatelmas
force-pushed
the
ferhat/lc-executor
branch
from
November 10, 2026 16:39
4aabbe9 to
62eb479
Compare
ferhatelmas
enabled auto-merge (squash)
November 10, 2026 16:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
feat
What is the current behavior?
#1627 and #1683 added the database operations and outbox needed for noncurrent lifecycle deletion but executor to run was missing.
What is the new behavior?
Add a bucket executor that evaluates archived versions, deletes eligible metadata in bounded batches and removes the corresponding backend artifacts.
Failed artifact deletions remain in the outbox for retry.
Additional context
Scheduling the executor and retry helper is a next separate change.