0.9.6

Summary

Update Node to 22.x.x

Changes

• Update Node to 22 (#111) by @renannoliveira

This release was made possible by the following contributors:

@renannoliveira

0.9.5

Summary

Update codeowners

Changes

• release 0.9.5 (#110) by @renannoliveira

This release was made possible by the following contributors:

@renannoliveira

v0.9.4

Summary

This release includes a dependency update for express to improve security and stability.
[Human readable summary of changes]

Changes

• chore: bump express to 4.20.0 (#109) by @fanfernandes

This release was made possible by the following contributors:

@dependabot[bot] and @fanfernandes

0.9.3

Summary

This releases introduces the auth token rotation which prevented users from using the plugin after 24h.

Changes

• fix: rotate oauth token when expired (#106) by @jhfgloria

This release was made possible by the following contributors:

@jhfgloria and @jpd4emis

0.9.2

Summary

This releases fixes a bug in package.json that was preventing the plugin from being installed in certain installations

Changes

• fix: relax version pinning of @pagerduty/backstage-plugin-common (#100) by @tamimkh
• fix pluginPackages type (#98) by @tamimkh

This release was made possible by the following contributors:

@tamimkh

0.9.1

Summary

This release introduces a few enhancements that to ensure a) no undesired code is executed when an exception is caught, and b) to avoid trying to emit headers multiple times.

Changes

• fix: add missing "return" statements after errors (#83) by @brianphillips

This release was made possible by the following contributors:

@brianphillips and @t1agob

0.9.0

Summary

This release introduces a set of features that were in a way dependent on each other which makes it quite large when compared to a typical release.

• Automated Backstage integration setup for mapped entities: With the goal of simplifying the setup process for mapped entities we introduced a feature that automatically creates a integration on the corresponding PagerDuty service when a pagerduty.com/service-id property is available.

  With this feature, admins can skip the step of creating an integration in PagerDuty and copy the integration key to each Backstage entity file. They can now simply add the pagerduty.com/service-id annotation to their service, or simply use the PagerDutyPage to map existing PagerDuty services to Backstage entities and the plugin will take care of the rest. This change is related to #80.

• Plugin configuration persistence layer: To support two-way sync for service dependencies we decided to give the admins the option of choosing which is their main source of truth and for that reason we introduced a new section in PagerDutyPage where you can specify your preferences. The backend centralises all the persistence layer and this release includes all the necessary methods for it.

• Two-way service dependency sync: This release introduces a way to keep your service dependencies in sync between PagerDuty and Backstage. Admins will be able to choose which source is the main one. This is an opt-in feature that you can enable on the PagerDutyPage under the configuration tab.

  ‼️ Important: Due to a Backstage design decision it is not possible to fully overwrite the relations specified in each entity's configuration file. For that reason the option to synchronise strictly from PagerDuty side is not available.

Changes

• feat: service dependency sync (#81) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.8.2

Summary

This release fixes some potential issues with JSON.parse on unsafe parameters that can lead to unexpected exceptions.

Changes

• chore: refactor JSON.parse usage on unsafe code (#77) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.8.1

Summary

This release bumps all Backstage packages to the latest version to allow an upgrade to 1.29.1 without any warnings on outdated packages.

Changes

• fix: bump deps to work with backstage v1.29.0 (#73) by @jpd4emis

This release was made possible by the following contributors:

@jpd4emis and @t1agob

0.8.0

Summary

This release introduces the necessary changes to support multi-account configurations.

• Plugin database now supports account reference
• All PagerDuty API operations are account aware
• Updated plugin configuration schema to accept multi-account configurations

We made extensive tests to ensure that the existing configuration for a single PagerDuty account still works. Therefore existing customers will be able to upgrade to the latest version without breaking anything.

Changes

• feat: add support for multiple accounts (#71) by @t1agob

This release was made possible by the following contributors:

@t1agob