Awesome Elixir has a "changelog" section under all projects. You can find it next to the "Repo" button in the header. There are two features that make it unique.

  1. It is an aggregation of parsed "CHANGELOG.md" files and releases information from Github. This way, it is easier to see all changes in a single place and a uniform style.
  2. All changelogs are "emojified". This helps with identifying each change easier. Emojification is achieved by parsing each line and applying a specific emoji based on the first word or some other tokens.

The combination of the above two makes package changelogs on Awesome Elixir unique.

As you know, an example is worth a 1,000 words ๐Ÿš€

Changelog examples

  • ethereumex 0.7.1 (October 10, 2021)
  • opq 3.3.0 (October 12, 2021)
    • [Added] The ability to start as part of a supervision tree
  • oban 2.9.0 (September 15, 2021)

    ๐Ÿ‘ท Optionally Use Meta for Unique Jobs

    ๐Ÿ‘ท It's now possible to use the meta field for unique jobs. Unique jobs have ๐Ÿ‘ท always supported worker, queue, and args fields. That was flexible, but ๐Ÿ‘ฎ forced applications to put ad-hoc unique values in args when they should really be in meta.

    ๐Ÿ‘ The meta field supports keys, just like args. That makes it possible to ๐Ÿ’… use highly efficient fingerprint style uniqueness (and possibly drop the index on args, if desired).

    ๐Ÿ–จ Here's an example of using a single "fingerprint" key in meta for uniqueness:

    defmodule MyApp.FingerprintWorker do
      use Oban.Worker, unique: [fields: [:worker, :meta], keys: [:fingerprint]]
    
      @impl Worker
      def new(args, opts) do
        fingerprint = :erlang.phash2(args)
    
        super(args, Keyword.put(opts, :meta, %{fingerprint: fingerprint}))
      end
    end
    

    0๏ธโƒฃ For backward compatiblity meta isn't included in unique fields by default.

    Expanded Start and Scale Options

    โ™ป๏ธ After extensive refactoring to queue option management and validation, now it's ๐Ÿ‘ possible to start and scale queues with all supported options. Previously ๐Ÿ‘ start/stop functions only supported the limit option for dynamic scaling, reducing runtime flexibility considerably.

    Now it's possible to start a queue in the paused state:

    Oban.start_queue(queue: :dynamic, paused: true)
    

    ๐Ÿ‘ Even better, for apps that use an alternative engine like the SmartEngine from Oban Pro, it's possible to start a dynamic queue with options like global concurrency or rate limiting:

    Oban.start_queue(queue: :dynamic, local_limit: 10, global_limit: 50)
    

    All options are also passed through scale_queue, locally or globally, even ๐Ÿ‘ allowing you to reconfigure a feature like rate limiting at runtime:

    Oban.scale_queue(queue: :dynamic, rate_limit: [allowed: 50, period: 60])
    

    โž• Added

    • [Oban] Add Oban.cancel_all_jobs/1,2 to cancel multiple jobs at once, within an atomic transaction. The function accepts a Job query for complete control over which jobs are cancelled.

    • [Oban] Add Oban.retry_all_jobs/1,2 to retry multiple jobs at once, within an atomic transaction. Like cancel_all_jobs, it accepts a query for fine-grained control.

    • [Oban] Add with_limit option to drain_queue/2, which controls the number of jobs that are fetched and executed concurrently. When paired with with_recursion this can drastically speed up interdependent job draining, i.e. workflows.

    • [Oban.Telemetry] Add telemetry span events for all engine and notifier actions. Now all database operations are covered by spans.

    • [Oban.Migrations] Add create_schema option to prevent automatic schema creation in migrations.

    ๐Ÿ”„ Changed

    • [Oban] Consistently include a :snoozed count in drain_queue/2 output. Previously the count was only included when there was at least one snoozed job.

    • โœ… [Oban.Testing] Default to attempt: 1 for perform_job/3, as a worker's perform/1 would never be called with attempt: 0.

    ๐Ÿ›  Fixed

    • [Oban.Queue.Supervisor] Change supervisor strategy to :one_for_all.

    Queue supervisors used a :rest_for_one strategy, which allowed the task supervisor to keep running when a producer crashed. That allowed duplicate long-lived jobs to run simultaneously, which is a bug in itself, but could also cause attempt > max_attempts violations.

    • ๐Ÿ”Œ [Oban.Plugins.Cron] Start step ranges from the minimum value, rather than for the entire set. Now the range 8-23/4 correctly includes [8, 12, 16, 20].

    • [Oban.Plugins.Cron] Correcly parse step ranges with a single value, e.g. 0 1/2 * * *

    • ๐Ÿ“‡ [Oban.Telemetry] Comply with :telemetry.span/3 by exposing errors as reason in metadata