Skip to content
Sarj Repo Standards
core/exception/expired

Renew or remove expired exceptions

A matching policy exception remains valid through the analysis date.

error

Examples

FlaggedFails
rule_id = "core/layout/non-overlapping-root"
component_id = "worker"
manifest_anchor = "components.worker.path"
fingerprint = "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
owner = "@example/payments"
reason = "migration in progress"
issue = "EXAMPLE-1"
created_on = "2029-01-01"
expires_on = "2029-03-01"
# analysis date: 2029-03-02
PassesClean
rule_id = "core/layout/non-overlapping-root"
component_id = "worker"
manifest_anchor = "components.worker.path"
fingerprint = "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"
owner = "@example/payments"
reason = "migration in progress"
issue = "EXAMPLE-1"
created_on = "2029-01-01"
expires_on = "2029-04-01"
# analysis date: 2029-03-02

Why it matters

The exception no longer suppresses its finding and leaves stale review metadata beside an active violation.

How detection works

Reports when an exception matching a current finding has an expires_on date earlier than the explicit analysis date.

What is inspected

  • A current finding, its exact matching exception, and an explicit analysis date.

Limits

  • Validating duplicate, unmatched, or future-dated exception records as findings.
  • An exception remains valid on its expires_on date.

How to fix it

Resolve the finding or renew its narrow exception through review.

  1. Fix the underlying finding and remove the exception, or extend its reviewed expiry without broadening its scope.

Verify

  • Run repo-lint check with the same explicit analysis date.