lvl0/fedi-feed-router
1
0
Fork 0
Code Issues 15 Pull requests Projects Releases 3 Packages Wiki Activity Actions

Release v1.3.0 #100

Merged
myrmidex merged 20 commits from release/v1.3.0 into main 2026-03-18 20:30:29 +01:00
Conversation 1 Commits 20 Files changed 111 +4002 -2030
myrmidex commented 2026-03-18 18:17:32 +01:00
Owner
Copy link

Summary

Automation, monitoring, and article management improvements:

  • #82 Feed health monitoring and notifications
  • #85 Configurable article validation rules (keyword filtering per route)
  • #89 Article cleanup and retention policy (30-day auto-cleanup)
  • #92 In-app notification infrastructure
  • #93 Feed staleness detection and alerts
  • #94 Publishing failure notifications
  • #96 Article triage UI — tabs, Clear, and Restore
  • #97 Auto-post filtered articles setting (per-route auto_approve)
  • #98 RouteArticle API endpoints for approve/reject/restore
  • #99 Move publish_status from Article to RouteArticle

Highlights

  • Keyword filtering pipeline: Routes can define keywords to filter articles. Matching articles land in the Pending tab for triage; non-matching are auto-rejected.
  • Per-route approval control: Global approval toggle + per-route auto_approve override for hands-off publishing.
  • In-app notifications: Feed staleness alerts, publishing failure notifications with notification bell in the UI.
  • Article cleanup: Daily job deletes articles older than 30 days with no pending/approved route articles.
  • Triage UI: Pending/All tabs with approve, reject, restore, and bulk clear actions.
## Summary Automation, monitoring, and article management improvements: - **#82** Feed health monitoring and notifications - **#85** Configurable article validation rules (keyword filtering per route) - **#89** Article cleanup and retention policy (30-day auto-cleanup) - **#92** In-app notification infrastructure - **#93** Feed staleness detection and alerts - **#94** Publishing failure notifications - **#96** Article triage UI — tabs, Clear, and Restore - **#97** Auto-post filtered articles setting (per-route auto_approve) - **#98** RouteArticle API endpoints for approve/reject/restore - **#99** Move publish_status from Article to RouteArticle ## Highlights - **Keyword filtering pipeline**: Routes can define keywords to filter articles. Matching articles land in the Pending tab for triage; non-matching are auto-rejected. - **Per-route approval control**: Global approval toggle + per-route `auto_approve` override for hands-off publishing. - **In-app notifications**: Feed staleness alerts, publishing failure notifications with notification bell in the UI. - **Article cleanup**: Daily job deletes articles older than 30 days with no pending/approved route articles. - **Triage UI**: Pending/All tabs with approve, reject, restore, and bulk clear actions.
myrmidex added this to the v1.3.0 milestone 2026-03-18 18:17:32 +01:00
myrmidex added the
enhancement
 label 2026-03-18 18:17:32 +01:00
myrmidex self-assigned this 2026-03-18 18:17:32 +01:00
myrmidex added 17 commits 2026-03-18 18:17:32 +01:00
94 - Add publishing failure notifications to job and listener
Some checks failed
CI / ci (push) Failing after 5m7s
Details
d21c054250
89 - Add article cleanup job with 30-day retention policy
Some checks failed
CI / ci (push) Failing after 4m35s
Details
CI / ci (pull_request) Failing after 4m23s
Details
cc94ba8e55
myrmidex added 1 commit 2026-03-18 18:43:43 +01:00
Fix CI lint by using ZTS PHP to match dev container
Some checks failed
CI / ci (push) Failing after 4m37s
Details
CI / ci (pull_request) Failing after 4m37s
Details
273fca76e3
myrmidex added 1 commit 2026-03-18 19:48:46 +01:00
Debug CI Pint environment
Some checks failed
CI / ci (push) Failing after 4m4s
Details
CI / ci (pull_request) Failing after 4m4s
Details
dfb87f4152
myrmidex added 1 commit 2026-03-18 20:01:53 +01:00
Fix Pint 1.29.0 lint issues and update CI workflow
All checks were successful
CI / ci (push) Successful in 5m52s
Details
CI / ci (pull_request) Successful in 5m46s
Details
Build and Push Docker Image / build (push) Successful in 4m6s
Details
d2919758f5
myrmidex commented 2026-03-18 20:13:34 +01:00
Author
Owner
Copy link

Code Coverage Report

Metric Value
Line Coverage 74.25%

Updated by CI — commit d2919758f5

<!-- ffr-ci-coverage-report --> ## Code Coverage Report | Metric | Value | |--------|-------| | **Line Coverage** | 74.25% | _Updated by CI — commit d2919758f5b7e013fa4130bf4d14784bcd3807e1_
myrmidex merged commit d2919758f5 into main 2026-03-18 20:30:29 +01:00
myrmidex deleted branch release/v1.3.0 2026-03-18 20:30:29 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
devops

All things Ci/CD

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
good first issue

Interested in contributing? Get started here.

  
next major release

Include in next Major Release

  
next minor release

Include in next minor release

  
question

More information is needed

  
testing

All sorts of testing: UI, automation, ...

No labels
bug
devops
duplicate
enhancement
good first issue
next major release
next minor release
question
testing
Milestone
Clear milestone
No items
No milestone
v1.3.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
myrmidex
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lvl0/fedi-feed-router#100
No description provided.
Delete branch "release/v1.3.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?