0.9.0

Summary

This release adds the type necessary for OAuth support in Backstage plugin configuration. Users can now configure the following OAuth parameters in Backstage app-config.yaml file.

pagerDuty:
  oauth:
    clientId: ${PD_CLIENT_ID}
    clientSecret: ${PD_CLIENT_SECRET}
    subDomain: ${PD_ACCOUNT_SUBDOMAIN}
    region: ${PD_ACCOUNT_REGION}           // Optional. allowed values: 'us', 'eu'. Defaults to 'us'.

It also introduces more friendly error messages when permissions for certain APIs or operations are not present. This was implemented not to break the PagerDuty Card experience.

Changes

• feat: add suport for scoped oauth (#70) by @t1agob
• fix: update error links to pagerduty docs (#66) by @codingdiaz

This release was made possible by the following contributors:

@codingdiaz and @t1agob

0.8.3

Summary

Version 0.8.3 fixes an issue that was causing an error message to show on-screen for user accounts that don't have AIOPs or Event Intelligence capabilities.

With this changes instead of getting an out-of-context error message users will see this image and message instead.

Changes

• refactor: improve error handling on client side for change events (#64) by @t1agob

This release was made possible by the following contributors:

@t1agob @yoramshai

0.8.2

Summary

Version 0.8.2 bumps the version of @pagerduty/backstage-plugin-common to version 0.0.2.

Version 0.0.1 had a misconfiguration that was forcing the backend plugin to load it as an ES6 module and while that's supported for the frontend it is not yet fully supported for backend plugins.

This dependency upgrade syncs the version of the common package between frontend and backend plugins.

Changes

• chore(deps): bumping up common package version to latest (#61) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.8.1

Summary

This minor release moves the direct REST API calls from the frontend component to the backend. Instead of leveraging the Backstage proxy to make direct API calls to PagerDuty the calls are made to the backend plugin instead.

This removes the dependency on the proxy and prevents other plugins from using the PagerDuty proxy configuration to call PagerDuty APIs directly for other purposes which raises few security concerns.

Therefore the proxy configuration for PagerDuty on app-config.yaml is no longer required and is in-fact deprecated.

Changes

• feat: migrate api calls (#59) by @t1agob
• chore(deps): bump follow-redirects from 1.15.3 to 1.15.4 (#57) by @dependabot

This release was made possible by the following contributors:

@dependabot, @dependabot[bot], @jcoelho93 and @t1agob

0.7.4

Summary

This release includes a fix to a bug (#54) that prevented the PagerDutyCard from refreshing when users leveraged the Backstage search to navigate between components.

Changes

• fix: component now refreshes when navigating from search (#55) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.7.3

Summary

This release updates the Backstage plugin configuration schema to add support for apiToken.

pagerDuty:
   apiToken: u+a81u12y4ax

The latest release of the backend plugin (0.2.0) required a schema change for the plugin to start successfully. It does not introduce new features or capabilities to this plugin but it makes sure that the schemas match and avoid misconfigurations.

Changes

• chore(schema): updated config schema to match backend plugin (#51) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.7.2

Summary

This release fixes an issue that prevented the installation of the plugin if the Backstage React version was not compatible with the plugin version. It also fixes a moderate security issue, adds support for React 18+ and bumps up the versions of Backstage packages.

Changes

chore(deps): add support for React 18+ (#43)
chore(deps): bump up Backstage versions (#44)
docs: Simplify readme file and point to full documentation (#47)
chore(deps): bump @adobe/css-tools from 4.3.1 to 4.3.2 (#48)
fix: move strict dependencies (#49)

This release was made possible by the following contributors:

@t1agob

0.7.1

Summary

With release 0.7.1 we have fixed some issues and added new capabilities to the oncall user list.

• List only users in escalation level 1 - these are the users that are actually oncall.
• Remove duplicate users from the oncall user list
• Add support for user profile picture and fallback to dummy avatar icon when an image is not provided.

Changes

• 🔧 fix: list only oncall users in plugin (#38) by @t1agob

This release was made possible by the following contributors:

@t1agob

0.7.0

Summary

This release marks the first version under PagerDuty's ownership of the Backstage plugin. You will not notice any major changes. Here's what we did:

• Fixed a bug that was preventing recent changes tab to show
• Removed double headers on plugin UI component for incidents and recent changes
• Patched potential security vulnerabilities on dependencies

Changes

🔧 Maintenance

• chore(release): release of v0.7.0 (#32) by @t1agob
• chore(deps): bump zod from 3.22.2 to 3.22.4 (#29) by @dependabot
• chore(deps): bump browserify-sign from 4.2.1 to 4.2.2 (#30) by @dependabot
• chore(deps): bump @babel/traverse from 7.22.20 to 7.23.2 (#26) by @dependabot
• chore(deps): bump postcss from 8.4.29 to 8.4.31 (#25) by @dependabot
• chore(ci): adding release drafter with config (#21) by @t1agob
• chore(deps)Bump graphql from 16.8.0 to 16.8.1 (#17) by @dependabot
• chore(ci): adding github action to publish package on new release (#20) by @t1agob
• chore(docs): adding CODEOWNERS (#19) by @t1agob
• chore(ci): changing release step to trigger on pr close and merge (#16) by @t1agob
• chore(ci): forcing npm registry by default (#13) by @t1agob
• chore(ci): Build and publish package to npm (#2) by @t1agob

🌟 Minor Changes

• fix(ui): Removing sub-headers from lists (#15) by @t1agob

This release was made possible by the following contributors:

@dependabot, @dependabot[bot] and @t1agob