v0.13.0

prepare v0.13.0 (#442)

v0.12.2

No changes from v0.12.0 except fixes to the release process. v0.12.0 is not usable, this version should be used instead.

v0.12.1

No changes from v0.12.0 except fixes to the release process. v0.12.0 is not usable, this version should be used instead.

v0.12.0

⚠️ Version 0.12.0 has breaking changes when running riverui as an embedded http.Handler or via a Docker image. The ghcr.io/riverqueue/riverui images no longer include Pro-specific functionality; Pro customers must use new riverqueue.com/riverproui images to access Pro features. The main type was also renamed from Server to Handler for correctness since it functions as an http.Handler. See details below.

Changed

• Go binary now built without debug symbols for a ~35% reduction in output size. PR #391.

• Breaking change: River UI has been split into two modules and two executables: riverui for OSS-only functionality, and riverproui which adds Pro-specific functionality through dependencies on riverqueue.com/riverpro. This change makes it far easier to continue extending the UI for everybody but especially for Pro-specific feature.

  As part of this, the Server and ServerOpts types were also renamed to
  Handler and HandlerOpts respectively. Users who embed riverui into
  their Go app as a handler will need to update their riverui.NewServer
  initialization to riverui.NewHandler and to provide an Endpoints option in
  riverui.HandlerOpts, using riverui.NewEndpoints(client, nil) for the OSS
  riverui functionality or riverproui.NewEndpoints(client, nil) with a
  riverpro.Client for riverpro functionality:

  handler, err := riverui.NewHandler(&riverui.HandlerOpts{
      // For OSS riverui:
      Endpoints: riverui.NewEndpoints(client, nil),
      // Or, for riverpro:
      Endpoints: riverproui.NewEndpoints(client, nil),
      // ... other options
  })

  This structure enables Pro-specific API handlers and feature flags to be added to the Pro endpoint bundle.

  Users who run River UI from a Docker image can continue using the published OSS ghcr.io/riverqueue/riverui images for OSS-only functionality, while those using River Pro will want to migrate to the riverqueue.com/riverproui Docker images which are now being published. The Pro images are hosted with a Docker repository that leverages the same credentials as the River Pro Go module server. For details on how to configure this, see the River UI docs.

  For users who directly run the published riverui executables (published as GitHub release artifacts), there are no riverproui equivalents; those who need one can build it directly from riverproui/cmd/riverproui in this repository. Alternatively, migrate to either the riverqueue.com/riverproui Docker images or embed the http.Handler in your app as shown above.

  As part of this change, all database queries were removed from riverui in favor of being implemented directly in the underlying OSS and Pro drivers. PR #379 and PR 400.

• For job kind and queue name searching, match input against substrings instead of only prefixes. Particularly for long names, this is far more convenient. PR #398.

Fixed

• Remove __riverUiBasePath and __riverUiAssetUrl global functions to eliminate Content Security Policy issues. The application now uses the existing JSON configuration approach consistently for all path resolution. PR #382.

v0.11.0

Changed

• Upgraded all dependencies.
• Compatibility with River Pro v0.15.0 and River v0.23.0.

v0.10.0

Added

• Added a flexible search filter UI for the job list. PR #344.
• Added riverlog middleware logs to the job detail UI via a new unified attempts list, rather than separate lists for errors, attempted by, and now logs. PR #346.
• Added a RIVER_JOB_LIST_HIDE_ARGS_BY_DEFAULT env and ServerOpts.JobListHideArgsByDefault setting to give the backend the ability to choose to hide args from the job list by default. This is useful if your args tend to be encoded or encrypted and not worth looking at in bulk. It can also be overridden in a new settings screen in the UI. PR #354.

Changed

• Job args and metadata on the job detail view now use an interactive collapsible JSON view rather than pretty-printing the entire payload on screen. For large payloads this is a better UX and doesn't disrupt the page flow by default. PR #351.

Fixed

• Corrected links on queue list page to use the TanStack Router <Link> component instead of raw <a> tags so that settings like path prefix will be respected. PR #353.

v0.9.0

Added

• Added a queue detail page with the ability to view queue stats. For River Pro customers, this page offers the ability to dynamically override concurrency limits and to view individual clients for each queue, along with how many jobs each is working. PR #326.

v0.8.1

Changed

• Updated JS dependencies.

Fixed

• Fix negative wait times in job timeline. PR #288.
• Fix occasionally incorrect job durations for errored jobs. PR #288.
• Improve display of job attempt errors. PR #291.

v0.8.0

Added

• Allow PG* env vars as an alternative to DATABASE_URL. PR #256.

Fixed

• Queue list columns no longer resize when pausing/resuming a queue. PR #286.

v0.7.0

Added

• Add support for basic auth to the riverui executable. Thanks Taras Turchenko! PR #241.

Changed

• Updated internal dependency of riverqueue/river to compensate for a change to baseservice.Archetype and a utility function. PR #253.