Skip to content

2026.5.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 May 15:37
· 28 commits to main since this release
2026.5.2
924d82d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Docker

docker pull ghcr.io/TheDuffman85/linux-update-dashboard:2026.5.2

Highlights

  • Added a new cron-based Schedules page for refresh, update, and notification delivery schedules.
  • Added scheduled notification delivery, allowing notification events to be batched instead of sent immediately.
  • Added support for assigning notification channels to multiple notification schedules.
  • Improved management table interactions across credentials, notifications, and schedules, including reorder/copy/edit/delete behavior and cleaner table overflow handling.

Scheduling

  • Added /api/schedules management endpoints for listing, creating, updating, deleting, and reordering schedules.
  • Added refresh schedules with scoped systems and configurable cache duration.
  • Added update schedules that refresh scoped systems and run upgrades where visible updates remain.
  • Added notification digest schedules that deliver pending events for assigned channels.
  • Migrated existing legacy refresh interval/cache settings into a default refresh schedule automatically.

Notifications

  • Unified notification delivery around schedule records.
  • Notification channels can now use immediate delivery or one or more cron-based notification schedules.
  • Added safer duplication of notification channels, including support for reusing stored sensitive config where appropriate.
  • Improved schedule labels and assignment handling in the notification editor.

Security & Reliability

  • Hardened schedule API validation, including server-side cron minimum interval enforcement.
  • Added LUDASH_MIN_SCHEDULE_INTERVAL_MINUTES with a default of 5.
  • Blocked API tokens from accessing schedule management endpoints.
  • Fixed toast ID generation on insecure origins where crypto.randomUUID may be unavailable. Fixes #136.
  • Documented HTTPS recommendations for browser-only features such as passkeys and clipboard access.

Commits Included

  • Add cron-based schedules and fix toast IDs on insecure origins by @TheDuffman85 in #149

Full Changelog: 2026.5.1...2026.5.2

Contributors

TheDuffman85
Assets 2
Loading