Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: 0.15.1 #133

Merged
merged 2 commits into from
Aug 21, 2024
Merged

release: 0.15.1 #133

merged 2 commits into from
Aug 21, 2024

Conversation

t1agob
Copy link
Contributor

@t1agob t1agob commented Aug 21, 2024

Description

This PR 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.

Acknowledgement

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

t1agob and others added 2 commits August 21, 2024 11:52
Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
### Description

This PR 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](https://github.com/PagerDuty/backstage-plugin-entity-processor/releases/tag/0.3.0)
of `@pagerduty/backstage-plugin-entity-processor` which is now fixed and
released on version
[0.3.1](https://github.com/PagerDuty/backstage-plugin-entity-processor/releases/tag/0.3.1).

**Issue number:** N/A

### Type of change

- [x] New feature (non-breaking change which adds functionality)
- [ ] Fix (non-breaking change which fixes an issue)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

### Checklist

- [x] I have performed a self-review of this change
- [x] Changes have been tested
- [ ] Changes are documented
- [x] Changes generate *no new warnings*
- [x] PR title follows [conventional commit
semantics](https://www.conventionalcommits.org/en/v1.0.0/)

If this is a breaking change 👇

- [ ] I have documented the migration process
- [ ] I have implemented necessary warnings (if it can live side by
side)

## Acknowledgement

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.

**Disclaimer:** We value your time and bandwidth. As such, any pull
requests created on non-triaged issues might not be successful.
@t1agob t1agob added the release Actions related to a release of a new version label Aug 21, 2024
@t1agob t1agob merged commit 2e9603a into main Aug 21, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Actions related to a release of a new version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant