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.12.1 #106

Merged
merged 5 commits into from
Jun 14, 2024
Merged

release: 0.12.1 #106

merged 5 commits into from
Jun 14, 2024

Conversation

t1agob
Copy link
Contributor

@t1agob t1agob commented Jun 14, 2024

Description

Version 0.12.1 updates all backstage dependencies to the latest version. The PR that originated this version was created based on customer request to update @backstage/core-components to version 0.14 (#102). We decided to use this opportunity to upgrade all packages.

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.

mdb and others added 5 commits May 6, 2024 06:44
This corrects the `it()` description associated with the PagerDuty API
client's handling of generic non-OK HTTP responses that are not 401s,
403s, or 404s. Previously, the test case claimed the client throws
`NotFoundError`s in such cases. This is not true; the client throws a generic
descriptive error in such cases.

Signed-off-by: Mike Ball <mikedball@gmail.com>
### Description

This corrects the `it()` description associated with the PagerDuty API
client's handling of generic non-OK HTTP responses that are not 401s,
403s, or 404s. Previously, the test case claimed the client throws
`NotFoundError`s in such cases. This is not true; the client throws a
generic descriptive error in such cases.

Thanks!

**Issue number:** (e.g. #123)

### Type of change

- [ ] New feature (non-breaking change which adds functionality)
- [x] 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
- [X] 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.
update @backstage/core-components to latest version

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

This PR updates @backstage/core-components to version 0.14 as request on
issue #102 and all other backstage dependencies.

**Issue number:** #102 

### Type of change

- [ ] New feature (non-breaking change which adds functionality)
- [x] 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 Jun 14, 2024
@t1agob t1agob self-assigned this Jun 14, 2024
@t1agob t1agob merged commit 3ad79e6 into main Jun 14, 2024
4 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.

2 participants