Que v2.2.0 Release Notes

Release Date: 2022-08-29 // almost 2 years ago
    • ๐Ÿ”„ Changed:
      • When migrating, now raises an exception when the Que DB schema version is missing from the database. The migrations system records this version in a comment on the que_jobs table. #379
        • > Que::Error: Cannot determine Que DB schema version. > > The que_jobs table is missing its comment recording the Que DB schema version. This is likely due to a bug in Rails schema dump in Rails 7 versions prior to 7.0.3, omitting comments - see https://github.com/que-rb/que/issues/363. Please determine the appropriate schema version from your migrations and record it manually by running the following SQL (replacing version as appropriate): > > COMMENT ON TABLE que_jobs IS 'version';
    • โœ‚ Removed:
      • Removed support for upgrading directly from a version of Que prior to v0.5.0 (released on 2014-01-14), which introduced the migrations system. It's too difficult to handle the different DB schemas from prior to this.
    • Internal:
      • Moved command_line_interface.rb from bin/ to lib/. #378

Previous changes from v2.1.0

    • โž• Added:
      • Added bulk enqueue interface for performance when enqueuing a large number of jobs at once - [docs](docs#enqueueing-jobs-in-bulk).
    • ๐Ÿ—„ Deprecated:
      • Deprecated que_state_notify trigger (que_state notification channel / job_change notification message). See #372. We plan to remove this in a future release - let us know on the issue if you desire otherwise.

    ๐Ÿš€ This release contains a database migration. You will need to migrate Que to the latest database schema version (7). For example, on ActiveRecord and Rails 6:

    class UpdateQueTablesToVersion7 < ActiveRecord::Migration[6.0]
      def up
        Que.migrate!(version: 7)
      def down
        Que.migrate!(version: 6)