fix(deps): update backstage monorepo to v2 (major)#47
Merged
Conversation
b31a13f to
0bc986c
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 contains the following updates:
^1.16.0→^2.0.0^1.8.0→^2.0.0Release Notes
backstage/backstage (@backstage/plugin-catalog-node)
v2.1.0Compare Source
Minor Changes
bf71677: Added the ability for SCM events subscribers to mark the fact that they have taken actions based on events, which produces output metrics:catalog.events.scm.actionswith attributeaction: Counter for the number of actions actually taken by catalog internals or other subscribers, based on SCM events. Theactionis currently eithercreate,delete,refresh, ormove.Patch Changes
v2.0.0Compare Source
Minor Changes
cfd8103: Promoted stable catalog extension points from alpha to main export. The following extension points are now exported from@backstage/plugin-catalog-nodeinstead of@backstage/plugin-catalog-node/alpha:catalogLocationsExtensionPointandCatalogLocationsExtensionPointcatalogProcessingExtensionPointandCatalogProcessingExtensionPointcatalogAnalysisExtensionPointandCatalogAnalysisExtensionPointThe old alpha exports for these extension points are now deprecated with
@deprecatedmarkers pointing to the new stable exports. Please update your imports from@backstage/plugin-catalog-node/alphato@backstage/plugin-catalog-node.Note: The
catalogModelExtensionPoint,catalogPermissionExtensionPoint, and related types remain in alpha.b4e8249: Implemented support for the newqueryLocationsandstreamLocationsthat allow paginated/streamed and filtered location queries34cc520: Introduced thecatalogScmEventsServiceRef, along withCatalogScmEventsServiceand associated types. These allow communicating a unified set of events, that parts of the catalog can react to.Patch Changes
42abfb1: UpdatedcatalogServiceMock.mockto usecreateServiceMockfrom@backstage/backend-test-utils, replacing the internal copy ofsimpleMock. Added@backstage/backend-test-utilsas an optional peer dependency.7455dae: Use node prefix on native importsbackstage/backstage (@backstage/plugin-search-backend)
v2.1.0Compare Source
Minor Changes
0fbcf23: Migrated OpenAPI schemas to 3.1.Patch Changes
a49a40d: Updated dependencyzodto^3.25.76 || ^4.0.0& migrated to/v3or/v4imports.v2.0.12Compare Source
Patch Changes
7455dae: Use node prefix on native imports8148621: Moved@backstage/backend-defaultsfromdependenciestodevDependencies.69d880e: Bump to latest zod to ensure it has the latest featuresv2.0.11Compare Source
Patch Changes
7455dae: Use node prefix on native imports69d880e: Bump to latest zod to ensure it has the latest featuresv2.0.10Compare Source
Patch Changes
v2.0.9Compare Source
Patch Changes
de96a60: chore(deps): bumpexpressfrom 4.21.2 to 4.22.0v2.0.8Compare Source
Patch Changes
b2bef92: Convert all enums to erasable-syntax compliant patterns05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v2.0.7Compare Source
Patch Changes
v2.0.6Compare Source
Patch Changes
0efcc97: Updated generated schemasv2.0.5Compare Source
Patch Changes
v2.0.4Compare Source
Patch Changes
69fb975: Error messages should not contain backend SQL query strings in the API response, this change will ensure that messages are logged and empty response is returned to the userv2.0.3Compare Source
Patch Changes
c83cd8b: Fixed some circular or otherwise unclear importsv2.0.2Compare Source
Patch Changes
v2.0.1Compare Source
Patch Changes
v2.0.0Compare Source
Major Changes
d5c4a9d: BREAKING Removed support for the legacy backend system and references to@backstage/backend-common, please migrate to the new backend system.Patch Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.