Releases: PagerDuty/backstage-plugin
0.15.5
Summary
[Human readable summary of changes]
Changes
- chore: update nodejs version to 22.15.0 (#157) by @renannoliveira
This release was made possible by the following contributors:
Contributors
Assets 2
0.15.4
Summary
Update codeowners
Changes
- Update codeowners (#156) by @renannoliveira
This release was made possible by the following contributors:
Contributors
Assets 2
0.15.3
Summary
This release includes all dependencies updates suggested by Dependabot (to date).
Changes
- release: 0.15.3 (#155) by @jhfgloria
- chore: bump dependencies (suggested by dependabot) (#154) by @jhfgloria
This release was made possible by the following contributors:
@dependabot[bot] and @jhfgloria
Contributors
Assets 2
0.15.2
Summary
This releases fixes a bug in package.json that was preventing the plugin from being installed in certain installations
Changes
- release: 0.15.2 (#149) by @tamimkh
- fix: relax version pinning of @pagerduty/backstage-plugin-common (#148) by @tamimkh
- fix: fix pluginPackages type (#146) by @tamimkh
This release was made possible by the following contributors:
Contributors
Assets 2
0.15.1
Summary
This release enables the PagerDuty option in the PagerDutyPage component settings which allows users to set PagerDuty as their main source for syncing service dependencies to Backstage.
This feature was disabled due to a limitation on version 0.3.0 of @pagerduty/backstage-plugin-entity-processor which is now fixed and released on version 0.3.1.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.15.0
Summary
This release updates the PagerDutyPage component to add a new configurations tab where users can configure how they want to sync service dependencies between Backstage and PagerDuty.
By default, service dependency syncing is disabled. It's an opt-in feature and admins need to be aware of what it does because you might end up deleting existing service dependencies on Backstage or PagerDuty.
On this release we also introduced a fix that was preventing users from showing/hiding columns on the service to entity mapping table (#123).
Changes
- refactor: disabled PagerDuty option due to a design limitation on Backstage (#127) by @t1agob
- fix: turned columnvisibility into a static object (#126) by @t1agob
- feat: service dependency sync (#125) by @t1agob
This release was made possible by the following contributors:
Contributors
Assets 2
0.14.1
Summary
This release refactors areas where JSON.parse was used in unsafe code which leaves the potential for unexpected exceptions.
It also bumps Backstage package versions and fixes a high severity security issue on a 3rd party dependency.
Changes
- chore(deps): bump fast-loops from 1.1.3 to 1.1.4 (#118) by @dependabot
- chore: remove json parse from unsafe code (#121) by @t1agob
This release was made possible by the following contributors:
@dependabot and @t1agob
Contributors
Assets 2
0.14.0
Summary
Release 0.14.0 introduces support for multi-account configuration. With this release, admins will be able to specify multiple PagerDuty accounts in the same Backstage instance. Support was added across all the components of the plugin:
- Backend: All API routes exposed take account as an optional parameter so you can create and query information from different PagerDuty Accounts. If admins leverage the Entity Mapping feature, the account is now persisted into the plugin database.
- Scaffolder Actions: When the scaffolder action is used on a template it now lists Escalation Policies from all accounts configured so the user can easily select the one they want. The Scaffolder action
also outputs the account so it can be replaced in theapp-config.yamlannotations. - Entity Processor: If an entity mapping stored in the plugin database contains the
accountproperty, the processor will add an annotation to the entity with its information.
This release solves an existing problem for many large organizations that have several PagerDuty accounts for segregation purposes or that result from company acquisitions.
Changes
This release was made possible by the following contributors:
Contributors
Assets 2
0.13.0
Summary
Release 0.13.0 introduces a PagerDutyPage component which can be added to your Backstage menu and allows users to explore advanced PagerDuty configurations. With this release we are adding support for Entity mapping which allows users to easily map existing PagerDuty services to Backstage entities without requiring updates to each service config file.
Below is an example of how the PagerDutyPage looks like when added to a Backstage instance.
Users will be able to see if the entity definition is up to date with the configuration in file or not and chose to persist the changes by manually creating a PR in the source code.
This release also applies a few security patches related to Backstage dependencies.
Changes
- docs: update readme with mapping capability (#114) by @t1agob
- feat: advanced config page (#113) by @t1agob
- chore(deps): bump ws from 8.14.2 to 8.17.1 (#112) by @dependabot
This release was made possible by the following contributors:
@dependabot, @dependabot[bot] and @t1agob
Contributors
Assets 2
0.12.2
Summary
This release includes a security patch and a bug fix that was allowing users to create incidents without defining the description of incidents after they created the first one. The state of the description property is now being cleaned up on successful incident creation.
Changes
- chore(deps): bump braces from 3.0.2 to 3.0.3 (#107) by @dependabot
- fix: ensures incident description state is cleaned after an incident is triggered (#108) by @t1agob
This release was made possible by the following contributors:
@dependabot, @dependabot[bot] and @t1agob