Version Packages #1
Open
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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 publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@backstage/catalog-model@0.3.0
Minor Changes
Patch Changes
1185919: Marked the
Groupentity fieldsancestorsanddescendantsfor deprecation on Dec 6th, 2020. See Remove requirements for Group model backstage/backstage#3049 for details.Code that consumes these fields should remove those usages as soon as possible. There is no current or planned replacement for these fields.
The BuiltinKindsEntityProcessor has been updated to inject these fields as empty arrays if they are missing. Therefore, if you are on a catalog instance that uses the updated version of this code, you can start removing the fields from your source catalog-info.yaml data as well, without breaking validation.
After Dec 6th, the fields will be removed from types and classes of the Backstage repository. At the first release after that, they will not be present in released packages either.
If your catalog-info.yaml files still contain these fields after the deletion, they will still be valid and your ingestion will not break, but they won't be visible in the types for consuming code.
@backstage/plugin-kubernetes@0.3.0
Minor Changes
Patch Changes
@backstage/plugin-kubernetes-backend@0.2.0
Minor Changes
Patch Changes
@backstage/backend-common@0.3.1
Patch Changes
@backstage/catalog-client@0.3.1
Patch Changes
@backstage/cli@0.3.1
Patch Changes
lerna.jsonandpackage.jsonworkspace paths.versions:checkandversions:bumpcommands to simplify version management and avoid conflicts@backstage/core@0.3.2
Patch Changes
@backstage/plugin-api-docs@0.2.2
Patch Changes
@backstage/plugin-auth-backend@0.2.3
Patch Changes
@backstage/plugin-catalog@0.2.3
Patch Changes
@backstage/plugin-catalog-backend@0.2.2
Patch Changes
0c21212: Add support for reading groups and users from the Microsoft Graph API.
1185919: Marked the
Groupentity fieldsancestorsanddescendantsfor deprecation on Dec 6th, 2020. See Remove requirements for Group model backstage/backstage#3049 for details.Code that consumes these fields should remove those usages as soon as possible. There is no current or planned replacement for these fields.
The BuiltinKindsEntityProcessor has been updated to inject these fields as empty arrays if they are missing. Therefore, if you are on a catalog instance that uses the updated version of this code, you can start removing the fields from your source catalog-info.yaml data as well, without breaking validation.
After Dec 6th, the fields will be removed from types and classes of the Backstage repository. At the first release after that, they will not be present in released packages either.
If your catalog-info.yaml files still contain these fields after the deletion, they will still be valid and your ingestion will not break, but they won't be visible in the types for consuming code.
Updated dependencies [1166fcc]
Updated dependencies [bff3305]
Updated dependencies [1185919]
Updated dependencies [b47dce0]
@backstage/plugin-catalog-graphql@0.2.2
Patch Changes
@backstage/plugin-circleci@0.2.2
Patch Changes
@backstage/plugin-cloudbuild@0.2.2
Patch Changes
@backstage/plugin-cost-insights@0.4.1
Patch Changes
@backstage/plugin-github-actions@0.2.2
Patch Changes
@backstage/plugin-jenkins@0.3.1
Patch Changes
@backstage/plugin-lighthouse@0.2.3
Patch Changes
@backstage/plugin-register-component@0.2.2
Patch Changes
@backstage/plugin-rollbar@0.2.3
Patch Changes
@backstage/plugin-scaffolder@0.3.1
Patch Changes
@backstage/plugin-scaffolder-backend@0.3.2
Patch Changes
@backstage/plugin-search@0.2.1
Patch Changes
@backstage/plugin-sentry@0.2.3
Patch Changes
@backstage/plugin-sonarqube@0.1.4
Patch Changes
@backstage/plugin-techdocs@0.2.3
Patch Changes
@backstage/plugin-techdocs-backend@0.2.2
Patch Changes
example-app@0.2.3
Patch Changes
example-backend@0.2.3
Patch Changes