release: 0.7.3 #52
Merged
release: 0.7.3 #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…age plugin in source
fix yarn conflict that is preventing merge due to main branch lock
revert unstable backstage package and its dependencies
changed release publishing to a manual process
- add support for profile images - refactor oncall user list behavior to only show users on escalation level 1 - remove duplicates from oncall user list
add support for react 18+ Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
* chore(dependencies): ⬆️ add support for react 18+ * chore(dependencies): 📌 upgrade backstage dependencies --------- Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
simplify readme file and point to full documentation Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
* chore(deps): bump @adobe/css-tools from 4.3.1 to 4.3.2 Bumps [@adobe/css-tools](https://github.com/adobe/css-tools) from 4.3.1 to 4.3.2. - [Changelog](https://github.com/adobe/css-tools/blob/main/History.md) - [Commits](https://github.com/adobe/css-tools/commits) --- updated-dependencies: - dependency-name: "@adobe/css-tools" dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Tiago Barbosa <t1agob@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* build(react): ➖ move react dependencies to peer and dev Strict dependencies caused installation to fail if react version doesn't match with Backstage installation version --------- Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
updated config schema to match backend plugin Signed-off-by: Tiago Barbosa <tbarbos@hotmail.com>
### Description The latest release of the backend plugin ([0.2.0](https://github.com/PagerDuty/backstage-plugin-backend/releases/tag/0.2.0)) required a schema change for the plugin to start successfully. It does not introduce changes to the frontend plugin but this release makes sure that the schemas match. ### 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This release updates the Backstage plugin configuration schema to add support for
apiToken.The latest release of the backend plugin (0.2.0) required a schema change for the plugin to start successfully. It does
not introduce changes to the frontend plugin but this release makes sure that the schemas match.
Type of change
functionality to not work as expected)
Checklist
semantics
If this is a breaking change 👇
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.