Repository navigation
3.0: remove legacy compatibility paths #90
Description
Remove what remains for compatibility with 1.x and earlier deprecations:
AlertingConfig::email(recipient): deprecated since 2.0.0, because the target it creates cannot send without SMTP settings.- Stale-job reaper fallback: the reaper still reclaims rows that 1.x code claimed without a lease, using
started_atage (theolder_thanparameter). In 3.0, require that no 1.x workers remain (say so in the upgrade notes). The reaper can then rely on leases alone, andrequeue_stale_jobscan drop or repurpose itsolder_thanargument. - Audit for any other pre-2.0 fallbacks, such as rows without
next_run_atin cron rescheduling.
🤖 Generated with Claude Code
Activity
CodingAnarchy commentedon Oct 11, 2026
Also for 3.0:
JobArchiver::poolis a vestigial private field (every archiver operation takes the queue). Drop it along with theJobArchiver::new(pool)signature. Similarlyrate_per_minute(0)blocks forever; consider rejecting a zero rate at construction (API change). Noted in #99.CodingAnarchy commentedon Oct 11, 2026
From #87/#89 (PR #127): more fallbacks to remove in the legacy pass:
hammerwork-webJobHistory(now crate-private after 3.0: make cargo-hammerwork and hammerwork-web internals private #88) has defaults "for implementations that predate this method" (count_archivable,running_jobs,jobs_with_status,job_states). Implement on every backend and drop the defaults.MigrationRunnerno-opacquire_migration_lock/release_migration_lockdefaults: check whether external runners are supported; if not, seal and remove.cargo docwarnings in cargo-hammerwork (links to privateJobData/JOB_DATA_COLUMNSin commands/backup.rs, unresolvedrow_to_jsonin utils/job_rows.rs).feat!: remove legacy compatibility paths (#90) (#129)