Skip to content

Releases: line/promgen

v0.73.0 - 2026-03-10

10 Mar 10:38
0fb1385

Choose a tag to compare

⚠️ There are important changes in this release. Please keep reading. ⚠️

This release enforces the permission checks. Make sure that all Service and Project objects have their members properly set before updating to this release, otherwise some of your users will be unable to access their objects and will need to contact a Promgen admin for help. API users will also need to provide "Token" credentials in their queries.

Changelog:

  • [INTERNAL] Bump docker/build-push-action from 6.19.2 to 7.0.0 #709
  • [INTERNAL] Bump docker/login-action from 3.7.0 to 4.0.0 #708
  • [INTERNAL] Bump docker/metadata-action from 5.10.0 to 6.0.0 #707
  • [IMPROVEMENT] Add documentation Email and Slack notifiers #705
  • [IMPROVEMENT] Add migration check #704
  • [IMPROVEMENT] Sort the Probe list #703
  • [BUGFIX] Add missing migration for MetricSample model #702
  • [IMPROVEMENT] Support multiple PagerDuty back ends #700
  • [INTERNAL] Bump docker/build-push-action from 6.18.0 to 6.19.2 #698
  • [IMPROVEMENT] Show default value when Exporter's path is empty #696
  • [IMPROVEMENT] Fix UI quirks when showing notifier's value #695
  • [IMPROVEMENT] Add per-object permission checks #658

v0.72.4 - 2026-02-17

17 Feb 09:30
539caa1

Choose a tag to compare

This is still a transitional release: permission checks are not yet applied.

Changelog:

  • [IMPROVEMENT] Add Alertmanager notifier #694
  • [IMPROVEMENT] Pin Ruff's version #693
  • [INTERNAL] Bump docker/login-action from 3.6.0 to 3.7.0 #691
  • [IMPROVEMENT] Automatically set created_by field when creating new Silence #688
  • [IMPROVEMENT] Notifiers: Add support for PargerDuty #686
  • [INTERNAL] Bump actions/setup-python from 6.1.0 to 6.2.0 #690
  • [INTERNAL] Bump actions/checkout from 6.0.1 to 6.0.2 #689
  • [IMPROVEMENT] Alert notifications instrumentation #687
  • [IMPROVEMENT] Implement a Retry Mechanism for Celery Tasks #680
  • [BUGFIX] Registering an invalid URL causes an internal error #685
  • [IMPROVEMENT] Add Merge Users feature #683
  • [DOCUMENTATION] Add Promgen Task Queues explanation #684
  • [INTERNAL] Bump actions/checkout from 5.0.1 to 6.0.1 #682
  • [INTERNAL] Bump actions/setup-python from 6.0.0 to 6.1.0 #679
  • [INTERNAL] Bump docker/metadata-action from 5.8.0 to 5.10.0 #678
  • [INTERNAL] Bump actions/checkout from 5.0.0 to 5.0.1 #676
  • [BUGFIX] Fix overflow issue in the User Column of the Audit Table #675
  • [IMPROVEMENT] Show Alert's raw data inside modal #674
  • [IMPROVEMENT] Use fixed layout for Audit logs table #673
  • [IMPROVEMENT] Fix UI quirks in some tables #672
  • [BUGFIX] Wrong alert rule operator in docs example #671

v0.72.3 - 2025-11-07

07 Nov 08:29
a2d532c

Choose a tag to compare

This is still a transitional release: permission checks are not yet applied.

Changelog:

  • [IMPROVEMENT] Document permission system #668
  • [SECURITY] Update django to 4.2.26 #667
  • [BUGFIX] User notifier stops working after changing username #665
  • [BUGFIX] Some links from audit logs don't work #664
  • [BUGFIX] User may end up with two different permissions #663
  • [BUGFIX] Project owner without admin permission #661
  • [IMPROVEMENT] Add Audit Logs when assigning or removing permission for a Group #662

v0.72.2 - 2025-10-16

16 Oct 05:05
b0c24fe

Choose a tag to compare

This is still a transitional release: permission checks are not yet applied.

Highlights of this release:

We have fixed a bug that occurs when you try to delete a Project that does not have a linked Farm.

Changelog:

  • [BUGFIX] Fix deleting projects without farm #659

v0.72.1 - 2025-10-02

02 Oct 05:41
c261170

Choose a tag to compare

This is still a transitional release: permission checks are not yet applied.

Highlights of this release:

  • Users can be organized in Groups (in a similar way as Teams in Grafana).
  • Groups can be added as members of Services and Projects.
  • Farms are direct children of the Project they belong to. No need to set owner and members of a Farm.
  • All Farms in the DB without an assigned Project (orphan Farms) will be deleted.

Changelog:

  • [BUGFIX] Remove excluded "farm" field from ProjectSerializer #657
  • [IMPROVEMENT] Always use same confirmation question to delete Farm #655
  • [INTERNAL] Bump docker/login-action from 3.5.0 to 3.6.0 #654
  • [IMPROVEMENT] Use One-To-One relationship between Farm and Project #652
  • [IMPROVEMENT] Prevent users from accessing the default group #653
  • [IMPROVEMENT] Prevent future errors in migration files #651
  • [IMPROVEMENT] Clean up orphan farms #650
  • [IMPROVEMENT] Prevent future problems with remove_farm_perms migration #649
  • [IMPROVEMENT] Make farm a child of project #648
  • [IMPROVEMENT] Support searching for Groups #647
  • [INTERNAL] Bump actions/setup-python from 5.6.0 to 6.0.0 #645
  • [IMPROVEMENT] Integrate per-object-permission with the Group model #644
  • [BUGFIX] Allow filtering Group in Audit Logs #643
  • [IMPROVEMENT] Add organizing users in groups #641
  • [BUGFIX] Fix wrong formatted string in locale file #642
  • [IMPROVEMENT] Add auto-complete box for choosing user #639
  • [INTERNAL] Bump actions/upload-pages-artifact from 3.0.1 to 4.0.0 #638
  • [BUGFIX] Add superusers to UserPermissionForm's choices #640

v0.72.0 - 2025-08-18

18 Aug 01:27
5599365

Choose a tag to compare

This is a transitional release.

Users will have the possibility to add members to their Services, Projects and Farms, along with a designated role (Admin, Editor and Viewer).
On this release, permission checks will not be enforced. This is to allow the memberships to be populated by anyone, otherwise only the owner of an object would have permissions to see it, and many users would be blocked out. This could be specially critical in the case where the owner of an object is not up to date. Therefore, to avoid that issue we decided to not enforce the permission checks and allow the membership list to be populated before the next release.

Full changelog is below:

  • [IMPROVEMENT] Check ruff format in GitHub Actions #636
  • [IMPROVEMENT] Run ruff lint in GitHub Actions #635
  • [IMPROVEMENT] Support changing member's role on UI #634
  • [IMPROVEMENT] Add audit logs when assigning or removing permissions #633
  • [IMPROVEMENT] Keep parent info in audit logs #632
  • [INTERNAL] Bump actions/checkout from 4.2.2 to 5.0.0 #631
  • [BUGFIX] Perform settings override as a last action #630
  • [IMPROVEMENT] Allow defining members for Service, Project and Farm #626
  • [IMPROVEMENT] Activate a tab based on the hash value of the URL #629
  • [INTERNAL] Bump docker/login-action from 3.4.0 to 3.5.0 #627
  • [INTERNAL] Bump docker/metadata-action from 5.7.0 to 5.8.0 #628
  • [IMPROVEMENT] Support all operators for silences #620
  • [IMPROVEMENT] Using only one UI for showing Active Silences #624
  • [IMPROVEMENT] Add Edit button when showing the rule list #623

v0.71.0 - 2025-07-02

02 Jul 01:12
eaa3177

Choose a tag to compare

Changelog

  • [BUGFIX] Add missing opening div tag #621
  • [IMPROVEMENT] Sort the Farm's sources on the Project Detail page #618
  • [IMPROVEMENT] Organize the Project Detail Page with Tabs #617
  • [IMPROVEMENT] Move buttons to Rule Detail page from Rule Update page #619
  • [BUGFIX] Make notifier's filters not editable if 'show_edit' is false #616
  • [SECURITY] Not provide query results when testing Rule #614
  • [BUGFIX] Fix error messages showed when testing a site rule #615
  • [BUGFIX] Remove empty row when registering a new project #613
  • [BUGFIX] Fix shard unchecked when updating a project with an invalid form #612
  • [BUGFIX] Fix the breadcrumb of the Service Update page #611
  • [BUGFIX] Global messages: Use the right CSS class for errors #610
  • [IMPROVEMENT] Python files cleanup #609
  • [IMPROVEMENT] Align the form field with its label #608

v0.70.0 - 2025-06-04

04 Jun 08:19
7759654

Choose a tag to compare

Warning

This release includes breaking changes. Make sure you read these release notes, specially the "Breaking changes" section at the bottom.

Changelog

  • [IMPROVEMENT] Make owner fields not nullable #581 ( ⚠️ breaking )
  • [IMPROVEMENT] Permission check for Alertmanager #595 ( ⚠️ breaking )
  • [IMPROVEMENT] Fix UI quirks in the Farm Register page #604
  • [IMPROVEMENT] Add 'Token' panel to UI #596
  • [IMPROVEMENT] Fix UI quirks in Farm detail page #602
  • [IMPROVEMENT] Set owner when adding external farms #599
  • [IMPROVEMENT] Improve the feature displaying data source load #597
  • [IMPROVEMENT] Preventing the browser from caching promgen.vue.js file #600
  • [IMPROVEMENT] Rename some buttons #598
  • [IMPROVEMENT] Disengage Farm Update from Project #594
  • [IMPROVEMENT] Use DRF's APIView for AlertReceiver API #591
  • [IMPROVEMENT] Fix LegacyKeyValueFormat warnings in Dockerfile #589
  • [CLEANUP] Delete the unused template file url_form.html #592
  • [BUGFIX] Fix external Farm linkage #605
  • [BUGFIX] Trim whitespaces of search input #593
  • [BUGFIX] "Home" link in some breadcrumbs redirects to "Services" page #588
  • [INTERNAL] Bump docker/build-push-action from 6.17.0 to 6.18.0 #601
  • [INTERNAL] Update CODEOWNERS #606
  • [INTERNAL] Bump docker/build-push-action from 6.16.0 to 6.17.0 #590
  • [INTERNAL] Bump docker/build-push-action from 6.15.0 to 6.16.0 #587
  • [INTERNAL] Bump actions/setup-python from 5.5.0 to 5.6.0 #586

Breaking changes

Owner fields not nullable

As we mentioned in the release notes for the previous release, the owner fields in the Service, Project, Sender and Farm objects could be null. This is not allowed anymore in this new release, so before updating please make sure all of those objects have an owner set.

Permission check for Alertmanager

If you are not using Promgen for routing alerts, this does not affect you.

From this release, Alertmanager will need a token to use Promgen's alert API. Typically, you configure some webhooks in Alertmanager to route alerts through Promgen. Now, those webhooks need to provide credentials.

As a first step, you need to go to Promgen's admin panel and create a new user account for Alertmanager. It doesn't matter which password you chose, since it won't be used at all. We recommend a user name like alertmanager_sa (which stands for Alertmanager Service Account), but you can chose any name you want.

Second step, you need to grant to that user account the promgen | alert | Can process alerts user permission.

Third step, you need to create a token for that user account.

With that token, you can now configure your Alertmanager's webhooks to provide credentials. Typically, in the alertmanager.yml file, you would have a receivers configuration similar to this one:

receivers:
  # Route alerts through Promgen
  - name: promgen
    webhook_configs:
    - url: <Your Promgen URL>/api/v1/alerts
      http_config:
        authorization:
          type: Token
          credentials: <The token you created on the third step>

v0.69.0 - 2025-04-25

25 Apr 02:26
2181cb4

Choose a tag to compare

  • [IMPROVEMENT] Return owner name in Farm API #583
  • [IMPROVEMENT] Add owner field to Farm object #582

Important notes

From this release, the Service, Project, Sender and Farm objects have an owner field. Currently, that field can be null.
However, in the next release we are going to enforce that field to be not null, to ensure all of those objects have an owner.
You won't be able to update to the next release if any of those objects doesn't have an owner. Therefore, please take your time and check that all of those objects in your Promgen instance have an owner before the next release.

v0.68.0 - 2025-03-13

13 Mar 07:55
4f5752c

Choose a tag to compare

  • [SECURITY] Remove 'authorization' field from the retrieve Shard API #576