Improvements
Reverb/Echo WebSocket config is now runtime-injected from the Laravel backend instead of baked into the JS bundle at Vite build time. The same Docker image now works in any deployment without rebuilding.
Release notes and changelog for Pricore.
Reverb/Echo WebSocket config is now runtime-injected from the Laravel backend instead of baked into the JS bundle at Vite build time. The same Docker image now works in any deployment without rebuilding.
This release makes Pricore realtime. Organization dashboards and repository pages now update live as syncs happen, powered by Laravel Reverb and WebSockets.
This release brings first-class GitLab support to Pricore. You can now connect GitLab repositories (including self-hosted instances), sign in with GitLab OAuth, and receive webhooks for automatic package syncing. The UI also received a visual refresh with warmer surfaces and improved typography.
This release focuses on the organization dashboard, adding a real-time activity feed and personalized package sidebar alongside improvements to package version details.
This release focuses on navigation and dashboard polish: a new command palette for quick access to everything, and a refreshed sync activity feed.
Redesigned Recent Syncs: status icons, duration, and version stats
Theme Toggle: switch between Light, Dark, and System from the user menu
This release focuses on UI polish across the application and adds better visibility into repository sync activity.
Stale Version Cleanup (#12): When branches or tags are deleted from a repository, the corresponding package versions are now automatically removed during sync and via GitHub webhooks.
Version Filters: Filter package versions by name, type (tag or branch) on the package detail page.
Smarter repository syncing — When a webhook fires, Pricore now compares each ref's commit SHA against existing package versions before syncing. Unchanged refs are skipped entirely, eliminating redundant API calls. A repo with 50 tags where only 1 changed now makes ~3 API calls instead of ~58.
Rate-aware GitHub API retry — The GitHub provider now reads X-RateLimit-Remaining and X-RateLimit-Reset headers. When rate-limited, it waits the correct duration instead of retrying blindly. A warning is logged when remaining requests drop below 100.