Version Packages#365
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
01edcf4 to
c86116f
Compare
3045110 to
603893e
Compare
603893e to
e4e7d2c
Compare
e4e7d2c to
07d34af
Compare
This file contains hidden or 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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@axis-backstage/plugin-readme@0.19.0
Minor Changes
b5e5411: Added a
hideIfNotFoundconfig option to the readme card extension forthe new frontend system. When set to
true, the entire card is hiddenwhen no README.md file is found, instead of showing an error message.
This is the NFS equivalent of the
isReadmeAvailableentity filteravailable in the old frontend system.
Example app-config.yaml:
app:
extensions: - entity-card:readme:
config:
hideIfNotFound: true
bb83b10: Migrated
ReadmeCardfrom the legacy MUIInfoCardtoEntityInfoCardfrom@backstage/plugin-catalog-react.The
variantandmaxHeightprops have been removed fromReadmeCardProps. Users relying on these props should switch toReadmeCardLegacyProps, which preserves the old behaviour and is accepted byReadmeCardfor backward compatibility. BothvariantandmaxHeightare deprecated and will be removed in a future release.Patch Changes
8a8e8da: NFS: Make the Readme entity card height configurable
The height of the entity card now defaults to the same height as
the legacy card. If used in NFS the height can be configured
using the config as follows:
@axis-backstage/plugin-statuspage@0.11.0
Minor Changes
d29962b: Add support for the new frontend system (NFS). The plugin can now be imported from the
./alphaentry point and registered as a feature in a new-system app.The plugin provides three extensions out of the box:
api:statuspage— registers theStatuspageClientpage:statuspage— mounts the full statuspage at/statuspageentity-card:statuspage— renders theStatuspageEntityCardon entity pagesConfigure the instance name for the page extension in
app-config.yaml:Patch Changes
@axis-backstage/plugin-jira-dashboard@2.3.4
Patch Changes
config:check --strictfailures caused by a schema collision between the frontend and backend Jira Dashboard config schemas. The frontend plugin no longer re-declares thejiraDashboardconfig key; it relies on the backend's schema, which already exposesannotationPrefixto the frontend.@axis-backstage/plugin-statuspage-backend@0.10.3
Patch Changes
app@0.12.8
Patch Changes
app-next@0.1.11
Patch Changes
backend@0.8.17
Patch Changes