fix(deps): update dependency @backstage/plugin-catalog-backend to v1.26.0 [security] #291
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.1
->1.26.0
GitHub Vulnerability Alerts
CVE-2024-45815
Impact
A malicious actor with authenticated access to a Backstage instance with the catalog backend plugin installed is able to interrupt the service using a specially crafted query to the catalog API.
Patches
This has been fixed in the
1.26.0
release of the@backstage/plugin-catalog-backend
package.References
If you have any questions or comments about this advisory:
Open an issue in the Backstage repository
Visit our Discord, linked to in Backstage README
Release Notes
backstage/backstage (@backstage/plugin-catalog-backend)
v1.26.0
Compare Source
Minor Changes
74acf06
: AdddependencyOf
prop to catalog model for Component kind to enable building relationship graphs with both directions usingdependsOn
anddependencyOf
.78475c3
: Allow offset mode paging in entity list providerbd35cdb
: Theanalyze-location
endpoint is now protected by thecatalog.location.analyze
permission.The
validate-entity
endpoint is now protected by thecatalog.entity.validate
permission.Patch Changes
1882cfe
: MovedgetEntities
ordering to utilize database instead of having it inside catalog clientPlease note that the latest version of
@backstage/catalog-client
will not order the entities in the same way as before. This is because the ordering is now done in the database query instead of in the client. If you rely on the ordering of the entities, you may need to update your backend plugin or code to handle this change.d425fc4
: Modules, plugins, and services are nowBackendFeature
, not a function that returns a feature.c2b63ab
: Updated dependencysupertest
to^7.0.0
.53cce86
: Fixed an issue with the by-query call, where ordering by a field that does not exist on all entities led to not all results being returnedUpdated dependencies
v1.25.2
Compare Source
This release fixes an issue where requests for the public
http
routes for theevents-backend
were authenticated causing 401 errors.v1.25.1
Compare Source
This release fixes an bug where the kubernetes plugin would crash reading
credentials
fromundefined
.v1.25.0
Compare Source
Minor Changes
163ba08
: DeprecatedRouterOptions
,CatalogBuilder
, andCatalogEnvironment
. Please make sure to upgrade to the new backend system.fc24d9e
: Stop using@backstage/backend-tasks
as it will be deleted in near future.Patch Changes
776eb56
:ProcessorOutputCollector
returns an error when receiving deferred entities that have an invalidmetadata.annotations
format.This allows to return an error on an actual validation issue instead of reporting that the location annotations are missing afterwards, which is misleading for the users.
389f5a4
: Update deprecated url-reader-related imports.93095ee
: Make sure node-fetch is version 2.7.0 or greatera629fb2
: Added setAllowedLocationTypes while introducing a new extension point called CatalogLocationsExtensionPoint51240ee
: Preserve defaultallowedLocationTypes
whensetAllowedLocationTypes()
ofCatalogLocationsExtensionPoint
is not called.Updated dependencies
v1.24.0
Compare Source
Minor Changes
b9ed1bb
: bumped better-sqlite3 from ^9.0.0 to ^11.0.0Patch Changes
v1.23.2
Compare Source
Patch Changes
v1.23.1
Compare Source
This release fixes an issue with the
@backstage/plugin-auth-backend
package, in particular theproviderInfo
not being set properly for some proxy providers.v1.23.0
Compare Source
Minor Changes
c7528b0
: Pass throughEventsService
too in the new backend systemPatch Changes
8869b8e
: Updated local development setup.78a0b08
: Internal refactor to handleBackendFeature
contract change.d44a20a
: Added additional plugin metadata topackage.json
.d779e3b
: Added a regex test to check commit hash. If url is from git commit branch ignore the edit url.6c5cab1
: Fix bug ingetLocationByEntity
0f55f5c
: Ensure name and title are both indexed by the DefaultCatalogCollator1779188
: Start using theisDatabaseConflictError
helper from the@backstage/backend-plugin-api
package in order to avoid dependency with the soon to deprecate@backstage/backend-common
package.v1.22.0
Compare Source
Minor Changes
f2a2a83
: Deprecated theLocationAnalyzer
type, which has been moved to@backstage/plugin-catalog-node
.f2a2a83
: The/alpha
plugin export has had its implementation of thecatalogAnalysisExtensionPoint
updated to reflect the new API.8d14475
: Emit well known relationships for the Domain entity kind.Patch Changes
131e5cb
: Fix broken links in README.c6cb568
: Add lifecycle monitoring for the catalog processingd229dc4
: Move path utilities frombackend-common
to thebackend-plugin-api
package.8479a0b
: Fixed bug in stitching queue gauge that included entities that are scheduled in the future.v1.21.1
Compare Source
Patch Changes
cfdc5e7
: Fixes an issue where/analyze-location
would incorrectly throw a 500 error on an invalid url.d5a1fe1
: Replaced winston logger withLoggerService
c52f7ac
: Make entity collection errors a little quieter in the logs.Instead of logging a warning line when an entity has an error
during processing, it will now instead emit an event on the event
broker.
This only removes a single log line, however it is possible to
add the log line back if it is required by subscribing to the
CATALOG_ERRORS_TOPIC
as shown below.Updated dependencies
v1.21.0
Compare Source
Minor Changes
f3e2e86
: Added the ability to inject custom permissions from modules, onCatalogBuilder
andCatalogPermissionExtensionPoint
Patch Changes
v1.20.0
Compare Source
Minor Changes
f3e2e86
: Added the ability to inject custom permissions from modules, onCatalogBuilder
andCatalogPermissionExtensionPoint
Patch Changes
v1.19.0
Compare Source
Minor Changes
9c7fb30
: Added the ability to inject custom permissions from modules, onCatalogBuilder
andCatalogPermissionExtensionPoint
Patch Changes
v1.18.0
Compare Source
Minor Changes
df12231
: Allow setting EntityDataParser using CatalogModelExtensionPoint15ba00f
: Migrated to support new auth services. TheCatalogBuilder.create
method now accepts adiscovery
option, which is recommended to forward from the plugin environment, as it will otherwise fall back to use theHostDiscovery
implementation.Patch Changes
2bd1410
: Removed unused dependencies999224f
: Bump dependencyminimatch
to v96f830bb
: Allow passing optional filter togetEntitiesByRefs
0fb419b
: Updated dependencyuuid
to^9.0.0
.Updated dependency
@types/uuid
to^9.0.0
.b65788b
: Move @backstage/repo-tools to dev dependencies280edeb
: Add index for original value in search table for faster entity facet responsedad018f
: Do not fail on stitching when the entity containsnull
values associated to deeply nested or long keys.v1.17.3
Compare Source
This release provides further fixes for the Gitiles integration, and relaxes the validation of the encoding of all query parameters of the catalog backend as well as allowing
limit=0
queries.v1.17.2
Compare Source
This release fixes an issue where certain Gerrit integration setups were broken, and where it was not possible to query multiple facets from the catalog at the same time.
v1.17.1
Compare Source
This release fixes an issue where the
EntitySwitch
component from@backstage/plugin-catalog
was preventing the display of entity errors. It also fixes the alphacatalogModuleTemplateKind
export from@backstage/plugin-scaffolder-backend
, which had incorrect plugin and module IDs.v1.17.0
Compare Source
Minor Changes
43dad25
: Add API to get location by entity126c2f9
: Updates the OpenAPI spec to use plugin asinfo.title
instead of package name.04907c3
: Updates the OpenAPI specification title to plugin ID instead of package name.d8a54d0
: Adds support for supplying field validators to the new backend's catalog plugin. If you're using entity policies, you should use the newtransformLegacyPolicyToProcessor
function to install them as processors instead.Patch Changes
9aac2b0
: Use--cwd
as the firstyarn
argument89b674c
: Minor performance improvement forqueryEntities
when the limit is 0.81e19b1
: Replace uses of deprecated types with replacements internally.efa8160
: Rollback the change for wildcard discovery, this fixes a bug with theAzureUrlReader
not working with wildcard pathsd208a93
: Fixed a bug wherefullTextFilter
wasn't preserved correctly in the cursor.6bb6f3e
: Updated dependencyfs-extra
to^11.2.0
.Updated dependency
@types/fs-extra
to^11.0.0
.1cae748
: Updated dependencygit-url-parse
to^14.0.0
.0a395b3
: Upgradedprom-client
to version 159b2eb3f
: Add support foronProcessingError
handler at the catalog plugin (new backend system).You can use
setOnProcessingErrorHandler
at thecatalogProcessingExtensionPoint
as replacement for
Updated dependencies
v1.16.2
Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.