5.1.1 (2025-07-17)

Bugfixes

• use correct build tags within build task for docker (af6ff26)

5.1.0 (2025-07-17)

Features

• reenable binaries for mips and mips64 (16a025e)

Bugfixes

• use build tags for sqlite and chai (a92651c)

5.0.0 (2025-07-16)

⚠ BREAKING CHANGES

• update billing github endpoints
• restructure build and release process

Features

• deps: update minor versions (#492) (dcabfe3)
• deps: update module github.com/google/go-github/v72 to v73 (#502) (2370470)
• deps: update module github.com/mgechev/revive to v1.11.0 (e471926)
• deps: update module github.com/oklog/run to v1.2.0 (#503) (e773469)
• deps: update module modernc.org/sqlite to v1.38.0 (#494) (fccc16e)
• restructure build and release process (56a256f)

Bugfixes

• deps: update golang docker tag to v1.24.5 (7f54b52)
• deps: update module github.com/golangci/golangci-lint/v2 to v2.2.2 (ada2988)
• deps: update module modernc.org/sqlite to v1.37.1 (#491) (9ef5a7c)
• deps: update patch versions (#495) (0bdb35a)
• update billing github endpoints (cb3d1c3)

Miscellaneous

• deps: bump github.com/go-chi/chi/v5 from 5.2.1 to 5.2.2 (ca9ac03)
• deps: pin dependencies (933da70)
• deps: update docker digests (ab87bb9)
• flake: updated lockfile [skip ci] (d371274)
• flake: updated lockfile [skip ci] (6c6ae51)
• flake: updated lockfile [skip ci] (da7e1b3)
• flake: updated lockfile [skip ci] (68525ac)
• flake: updated lockfile [skip ci] (e48bc34)
• flake: updated lockfile [skip ci] (89cac2d)
• flake: updated lockfile [skip ci] (388cd3a)
• flake: updated lockfile [skip ci] (de25547)
• update bingo deps and go version (31b2e2f)

Changelog for 4.1.1

The following sections list the changes for 4.1.1.

Summary

• Fix #485: Missing field updates for workflow jobs

Details

• Bugfix #485: Missing field updates for workflow jobs

  With the previous behavior the runner specific labels for worklow job metrics
  have always been empty. They we always set after the job started but have never
  been part of the database table update process.

  #485

Changelog for 4.1.0

The following sections list the changes for 4.1.0.

Summary

• Enh #443: Extra config option to change the database purge window
• Enh #469: Optional conclusion label for workflow jobs

Details

• Enhancement #443: Extra config option to change the database purge window

  We added a new option to optionally specify a different purge window for the
  database content if you are directly using a database source to read the metrics
  details.

  #443

• Enhancement #469: Optional conclusion label for workflow jobs

  We added another optional label which includes the conclusion value as an
  extra label as this could be different than the status value. This label got
  to be enabled by the --collector.workflow_jobs.labels flag or the
  GITHUB_EXPORTER_WORKFLOW_JOBS_LABELS environment variable.

  #469

Changelog for 4.0.1

The following sections list the changes for 4.0.1.

Summary

• Fix #413: Show errors for database ping
• Fix #414: Fix PostgreSQL identifiers to be bigint
• Fix #417: Runner ID was being set to run ID for workflow_job
• Fix #418: Include identifier in labels for workflow jobs
• Fix #418: Update conclusion and completed_at columns

Details

• Bugfix #413: Show errors for database ping

  To get more details why a ping to the database fails while starting the exporter
  we have added an error output to the logging.

  #413

• Bugfix #414: Fix PostgreSQL identifiers to be bigint

  Since Github submit 64bit integers for the identifier of workflow jobs we had to
  fix the type to BIGINT for the database schema to avoid errors related to
  store events.

  #414

• Bugfix #417: Runner ID was being set to run ID for workflow_job

  While implementing the workflow job collector we simply attached the wrong
  identifier to the runner id which was base on the run ID. Future webhooks will
  store the right ID now.

  #417

• Bugfix #418: Include identifier in labels for workflow jobs

  To avoid errors related to already scraped metrics we have added the identifier
  to the default labels for the workflow job collector.

  #418

• Bugfix #418: Update conclusion and completed_at columns

  For the new workflow job collector we had been missing the conclusion and
  completed_at values, they will be stored by future webhook events.

  #418

Changelog for 4.0.0

The following sections list the changes for 4.0.0.

Summary

• Chg #393: Switch to official logging library
• Chg #405: New metrics and configs for workflow job collector
• Chg #412: Change config and metric names for workflows
• Enh #368: Add actor.login label to workflow collector

Details

• Change #393: Switch to official logging library

  Since there have been a structured logger part of the Go standard library we
  thought it's time to replace the library with that. Be aware that log messages
  should change a little bit.

  #393

• Change #405: New metrics and configs for workflow job collector

  We have added a new metric for the duration of the time since the workflow job
  was created, defined in minutes. Beside that we have added two additional
  configurations to query the workflows for a specific status and you are able to
  define a different timeframe than 12 hours now.

  #405

• Change #412: Change config and metric names for workflows

  We introduced a BREAKING CHANGE by renaming the config variables and metrics
  related to the workflows. Previously you had to set --collector.workflows or
  GITHUB_EXPORTER_COLLECTOR_WORKFLOWS to enable the collector, for being
  consistent with the new workflow job collector we have renamed them to
  --collector.workflow_runs and GITHUB_EXPORTER_COLLECTOR_WORKFLOW_JOBS, so be
  aware about that. Additionally we have also renamed the metrics a tiny bit
  matching the same suffix. We renamed them as an example from
  github_workflow_status to github_workflow_run_status.

  #412

• Enhancement #368: Add actor.login label to workflow collector

  Export an actor.login label for workflow collector which could be added to the
  labels optionally, please keep the label cardinality in mind while enabling this
  label.

  #368

Changelog for 3.1.2

The following sections list the changes for 3.1.2.

Summary

• Fix #296: Drop out of order event if same timestamp as existing completed event

Details

• Bugfix #296: Drop out of order event if same timestamp as existing completed event

  We've fixed the behavior of out of order workflow events with the same
  timestamp, by preferring an already recorded completed event

  #296
  #298
  #312

Changelog for 3.1.1

The following sections list the changes for 3.1.1.

Summary

• Fix #296: Drop out of order workflow webhook events
• Fix #300: Rename package followin upstream genji package

Details

• Bugfix #296: Drop out of order workflow webhook events

  We've fixed the behavior of out of order workflow events by dropping them, since
  the events order is not guaranteed by GitHub

  #296
  #298

• Bugfix #300: Rename package followin upstream genji package

  The upstream project of the genji database implementation have been renamed, to
  stay being able to upgrade the library we are force to rename it within this
  project as well. We keep the driver name compatible to existing installations.

  #300

Changelog for 3.1.0

The following sections list the changes for 3.1.0.

Summary

• Fix #278: Create SQLite directory if it doesn't exist
• Enh #277: Configurable labels for runner metrics
• Enh #281: Add metrics for workflow timestamps

Details

• Bugfix #278: Create SQLite directory if it doesn't exist

  We have integrated a fix to always try to create the directory for the SQLite
  database if it doesn't exist. The exporter will fail to start if the directory
  does not exist and if it fails to create the directory for the database file.

  #278

• Enhancement #277: Configurable labels for runner metrics

  Initially we had a static list of available labels for the runner metrics, with
  this change we are getting more labels like the GitHub runner labels as
  Prometheus labels while they are configurable to avoid a high cardinality of
  Prometheus labels. Now you are able to get labels for owner, id, name,
  os, status and optionally labels.

  #277

• Enhancement #281: Add metrics for workflow timestamps

  We added new metrics to show multiple timestamps for the workflows like when the
  workflow have been created, updated and started. Please look at the
  documentation for the exact naming of these new metrics.

  #281