updating latest versions and release notes

Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>

docs/release-notes/backend.md

@@ -1,5 +1,27 @@
 # Release notes for Backend plugin
 
+## > 0.8.0
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin-backend/releases/tag/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
+
+### Dependencies
+
+- `@pagerduty/backstage-plugin-common: 0.2.0`
+
 ## > 0.7.2
 
 [GitHub release](https://github.com/PagerDuty/backstage-plugin-backend/releases/tag/0.7.2)

docs/release-notes/common.md

@@ -1,5 +1,28 @@
 # Release notes for Common library
 
+## > 0.2.0
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin-common/releases/tag/0.2.0)
+
+### Summary
+
+This release adds type support for multi-account configuration for all aspects of the PagerDuty plugin for Backstage:
+
+- UI Components:
+ - `PagerDutyCard`
+ - `PagerDutySmallCard`
+- Entity Mapping Page
+- Entity Processor
+- Scaffolder Action
+
+With these changes users with multiple PagerDuty accounts can now configure their services in the same Backstage instance.
+
+### Changes
+
+- feat: add account field to PagerDuty types
+- chore(deps): Bump @azure/identity from 4.0.0 to 4.3.0
+- chore(deps): Bump braces from 3.0.2 to 3.0.3
+
 ## > 0.1.5
 
 [GitHub release](https://github.com/PagerDuty/backstage-plugin-common/releases/tag/0.1.5)

docs/release-notes/entity-processor.md

@@ -1,5 +1,37 @@
 # Release notes for Entity Processor module
 
+## > 0.2.1
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin-entity-processor/releases/tag/0.2.1)
+
+### Summary
+
+This release fixes an issue with the missing plugin config schema. Without it the Backstage instance will not load.
+
+### Changes
+
+- fix: add missing config schema
+
+### Dependencies
+
+- `@pagerduty/backstage-plugin-common: 0.2.0`
+
+## > 0.2.0
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin-entity-processor/releases/tag/0.2.0)
+
+### Summary
+
+This PR adds multi-account support on entity processor. Now if the `account` property exists in the database for the mapped entity it will get added as an annotation to the Backstage entity.
+
+### Changes
+
+- feat: add support for multi account
+
+### Dependencies
+
+- `@pagerduty/backstage-plugin-common: 0.2.0`
+
 ## > 0.1.0
 
 [GitHub release](https://github.com/PagerDuty/backstage-plugin-entity-processor/releases/tag/0.1.0)

docs/release-notes/frontend.md

@@ -1,5 +1,29 @@
 # Release notes for Frontend plugin
 
+## > 0.14.0
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin/releases/tag/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 the `app-config.yaml` annotations.
+- **Entity Processor:** If an entity mapping stored in the plugin database contains the `account` property, 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
+
+- feat: add support for multi-account
+
+### Dependencies
+
+- `@pagerduty/backstage-plugin-backend: 0.8.0`
+- `@pagerduty/backstage-plugin-common: 0.2.0`
+
 ## > 0.13.0
 
 [GitHub release](https://github.com/PagerDuty/backstage-plugin/releases/tag/0.13.0)

docs/release-notes/scaffolder-actions.md

@@ -1,5 +1,27 @@
 # Release notes for Scaffolder Actions module
 
+## > 0.2.0
+
+[GitHub release](https://github.com/PagerDuty/backstage-plugin-scaffolder-actions/releases/tag/0.2.0)
+
+### Summary
+
+This PR adds support for multi-account configuration to scaffolder actions. It introduces no changes for the end user and adapts to the configuration set in `app-config.yaml`. If multiple accounts are configured the user will see the list of all Escalation Policies in all accounts with the reference to it's source account.
+
+<img width="273" alt="multi-account escalation policy list" src="https://github.com/user-attachments/assets/61b6139e-e0ad-44a9-86ec-f1004b380e0f">
+
+At creation time, the scaffolder will select the correct account to deploy the service to depending on the select escalation policy/account pair selected.
+
+### Changes
+
+- feat: add support for multi accounts
+- chore(deps): Bump mysql2 from 3.9.2 to 3.9.7
+- chore(deps): Bump mysql2 from 3.9.7 to 3.10.0
+
+### Dependencies
+
+- `@pagerduty/backstage-plugin-common: ^0.2.0`
+
 ## > 0.1.2
 
 [GitHub release](https://github.com/PagerDuty/backstage-plugin-scaffolder-actions/releases/tag/0.1.2)

overrides/main.html

@@ -3,7 +3,7 @@
 {% block announce %}
 <div>
  <p>
- <strong>🎉 New release!</strong> <span style="margin-left: 20px;"> Checkout the latest versions for Frontend(<a href="/backstage-plugin-docs/release-notes/frontend/#0130">0.13.0</a>), Backend(<a href="/backstage-plugin-docs/release-notes/backend/#072">0.7.2</a>), Common(<a href="/backstage-plugin-docs/release-notes/common/#015">0.1.5</a>), Scaffolder Actions(<a href="/backstage-plugin-docs/release-notes/scaffolder-actions/#012">0.1.2</a>) and Entity Processor(<a href="/backstage-plugin-docs/release-notes/entity-processor/#010">0.1.0</a>) </span>
+ <strong>🎉 New release!</strong> <span style="margin-left: 20px;"> Checkout the latest versions for Frontend(<a href="/backstage-plugin-docs/release-notes/frontend/#0140">0.14.0</a>), Backend(<a href="/backstage-plugin-docs/release-notes/backend/#080">0.8.0</a>), Common(<a href="/backstage-plugin-docs/release-notes/common/#020">0.2.0</a>), Scaffolder Actions(<a href="/backstage-plugin-docs/release-notes/scaffolder-actions/#021">0.2.1</a>) and Entity Processor(<a href="/backstage-plugin-docs/release-notes/entity-processor/#021">0.2.1</a>) </span>
  </p>
 </div>
 {% endblock %}