Skip to content

chore: Update all minor dependency updates #230

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Update all minor dependency updates #230

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 20, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@backstage-community/plugin-github-actions (source) ^0.15.0 → ^0.19.0 age confidence
@backstage/backend-defaults (source) ^0.12.0 → ^0.15.0 age confidence
@backstage/cli (source) ^0.34.1 → ^0.35.0 age confidence
@backstage/plugin-api-docs (source) ^0.12.10 → ^0.13.0 age confidence
@backstage/plugin-auth-backend (source) ^0.25.3 → ^0.26.0 age confidence
@backstage/plugin-scaffolder-node (source) ^0.11.2 → ^0.12.0 age confidence
@backstage/theme (source) ^0.6.8 → ^0.7.0 age confidence
pg (source) 8.16.3 → 8.17.2 age confidence
yarn (source) 4.10.3 → 4.12.0 age confidence

Release Notes

backstage/community-plugins (@​backstage-community/plugin-github-actions)

v0.19.0

Compare Source

Minor Changes
  • 55c0c3b: Backstage version bump to v1.46.1

v0.18.0

Compare Source

Minor Changes
  • 88fe001: Backstage version bump to v1.45.1

v0.17.0

Compare Source

Minor Changes

  • 5724534: Added a config for the entity content extension to change component layout between table and cards.

    Breaking Changed the name of the entity content extension from entity-content:github-actions/github-actions-entity-content to entity-content:github-actions.

v0.16.0

Compare Source

Minor Changes
  • f6232fc: Backstage version bump to v1.44.0
backstage/backstage (@​backstage/backend-defaults)

v0.15.0

Compare Source

Minor Changes

  • 6fc00e6: Added action filtering support with glob patterns and attribute constraints.

    The ActionsService now supports filtering actions based on configuration. This allows controlling which actions are exposed to consumers like the MCP backend.

    Configuration example:

    backend:
  actions:
    pluginSources:
      - catalog
      - scaffolder
    filter:
      include:
        - id: 'catalog:*'
          attributes:
            destructive: false
        - id: 'scaffolder:*'
      exclude:
        - id: '*:delete-*'
        - attributes:
            readOnly: false

    Filtering logic:

    • include: Rules for actions to include. Each rule can specify an id glob pattern and/or attributes constraints. An action must match at least one rule to be included. If no include rules are specified, all actions are included by default.
    • exclude: Rules for actions to exclude. Takes precedence over include rules.
    • Each rule combines id and attributes with AND logic (both must match if specified).

  • 27f9061: BREAKING: The constructor for FetchUrlReader is now private. If you have to construct an instance of it, please use FetchUrlReader.fromConfig instead.

  • 27f9061: BREAKING: coreServices.urlReader now validates that redirect chains are subject to the allow list in reading.allow of your app config. If you were relying on redirects that pointed to URLs that were not allowlisted, you will now have to add those to your config as well.

    Example:

     backend:
   reading:
     allow:
       - host: example.com
+      - host: storage-api.example.com
Patch Changes

v0.14.1

Compare Source

Patch Changes

v0.14.0

Compare Source

Minor Changes

  • fa43826: Move better-sqlite3 from dependencies to peer dependencies

  • 2bc4e02: BREAKING The correct configuration options for Valkey are now being used.

    These changes are required to app-config.yaml:

    backend:
  cache:
    store: valkey
    connection: ...
    client:
-     namespace: 'my-app'
-     keyPrefixSeparator: ':'
+     keyPrefix: 'my-app:'
-     clearBatchSize: 1000
-     useUnlink: false

    In comparison to Redis, Valkey requires the full keyPrefix including the separator to be specified instead of separate namespace and keyPrefixSeparator options. Also, Valkey does not support the clearBatchSize and useUnlink options.

Patch Changes

  • 37fba1d: Added support for Bitbucket Cloud OAuth. This introduces an alternative authentication method using a workspace OAuth consumer, alongside App Passwords (deprecated) and API tokens. OAuth does not require a bot or service account and avoids token expiry issues.

    BREAKING CHANGES

    • @​backstage/integration (src/bitbucketCloud/core.ts)

      • getBitbucketCloudRequestOptions now returns a Promise and must be awaited.

    • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud (src/actions/helpers.ts)

      • getBitbucketClient now returns a Promise and must be awaited.
      • getAuthorizationHeader now returns a Promise and must be awaited.

    OAuth usage example

    integrations:
  bitbucketCloud:
    - clientId: client-id
      clientSecret: client-secret

  • de96a60: chore(deps): bump express from 4.21.2 to 4.22.0

  • aa79251: build(deps): bump node-forge from 1.3.1 to 1.3.2

  • f96edff: Allow configuration of the referrerPolicy

  • fb029b6: Updated luxon types

  • d9759a1: BREAKING ALPHA: The old instanceMetadataService has been removed from alpha. Please switch over to using the stable coreServices.rootInstanceMetadata and related types instead, available from @backstage/backend-plugin-api.

  • 847a330: Fix for jose types

  • 25b560e: Internal change to support new versions of the logform library

  • 2a0c4b0: Adds a new experimental RootSystemMetadataService for tracking the collection of Backstage instances that may be deployed at any one time. It currently offers a single API, getInstalledPlugins that returns a list of installed plugins based on config you have set up in discovery.endpoints as well as the plugins installed on the instance you're calling the API with. It does not handle wildcard values or fallback values. The intention is for this plugin to provide plugin authors with a simple interface to fetch a trustworthy list of all installed plugins.

  • 3016a79: Updated dependency @types/archiver to ^7.0.0.

  • 42db6a6: Don't warn when parsing storeOptions for memory cache

  • Updated dependencies

v0.13.2

Compare Source

v0.13.1

Compare Source

Patch Changes

v0.13.0

Compare Source

Minor Changes

  • 2d3e2b2: implement support for direct url for AzureBlobStorageUrlReader search function

  • 8b91238: Adds support for configuring server-level HTTP options through the
    app-config.yaml file under the backend.server key. Supported options
    include headersTimeout, keepAliveTimeout, requestTimeout, timeout,
    maxHeadersCount, and maxRequestsPerSocket.

    These are passed directly to the underlying Node.js HTTP server.
    If omitted, Node.js defaults are used.

  • 8495b18: Add a new externalTokenHandlersServiceRef to allow custom external token validations

Patch Changes
backstage/backstage (@​backstage/cli)

v0.35.2

Compare Source

Patch Changes
  • 320c6a9: Bump @swc/core to support ES2023 and ES2024
  • c0d7bf6: Added --include and --format options to backstage-cli info command for including additional packages via glob patterns and outputting as JSON or Text.
  • f6a5d2f: Fixed CSS module class name collisions when running multiple versions of packages simultaneously by using content-based hashing for class name generation.
  • 140cbc2: Added @backstage/backend-test-utils to backend package templates.
  • 4eeba9e: Upgrade zod-validation-error to version 4
  • 9ee5996: Bump minimum required @swc/core to avoid transpilation bug
  • Updated dependencies

v0.35.1

Compare Source

Hey, I just made a Pull Request!

I created a module for Rails and one action to use rails new in the scaffolder

Addesd to the plugin list:
image

✔️ Checklist
  • A changeset describing the change and affected packages. (more info)
  • Added or updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)
  • All your commits have a Signed-off-by line in the message. (more info)

v0.35.0

Compare Source

Minor Changes

  • f6f22a9: Provide --no-node-snapshot by default when running the package start or package test. You can disable this behavior by providing NODE_OPTIONS='--node-snapshot'.

  • f8dff94: Switched the default module resolution to bundler and the module setting to ES2020.

    You may need to bump some dependencies as part of this change and fix imports in code. The most common source of this is that type checking will now consider the exports field in package.json when resolving imports. This in turn can break older versions of packages that had incompatible exports fields. Generally these issues will have already been fixed in the upstream packages.

    You might be tempted to use --skipLibCheck to hide issues due to this change, but it will weaken the type safety of your project. If you run into a large number of issues and want to keep the old behavior, you can reset the moduleResolution and module settings your own tsconfig.json file to node and ESNext respectively. But keep in mind that the node option will be removed in future versions of TypeScript.

    A future version of Backstage will make these new settings mandatory, as we move to rely on the exports field for type resolution in packages, rather than the typesVersions field.

  • cd0b8a1: BREAKING: jest is now a peer dependency. If you run tests using Backstage CLI, you must add Jest and its environment dependencies as devDependencies in your project.

    You can choose to install either Jest 29 or Jest 30. The built-in Jest version before this change was Jest 29, however, we recommend that you switch to Jest 30. Upgrading will solve the Could not parse CSS stylesheet errors, allow you to use MSW v2 in web packages, and ensure that you remain compatible with future versions of the Backstage CLI. Support for Jest 29 is temporary, with the purpose of allowing you to upgrade at your own pace, but it will eventually be removed.

    • Jest 29: Install jest@^29 and jest-environment-jsdom@^29. No migration needed, but you may see Could not parse CSS stylesheet warnings/errors when testing components from @backstage/ui or other packages using CSS @layer declarations.
    • Jest 30: Install jest@^30, @jest/environment-jsdom-abstract@^30, and jsdom@^27. Fixes the stylesheet parsing warnings/errors, but requires migration steps.

    See the Jest 30 migration guide for detailed migration instructions.

Patch Changes

  • de96a60: chore(deps): bump express from 4.21.2 to 4.22.0

  • e7db290: Add missing peer/dev dependencies to the frontend plugin template.

    react-dom was not declared as a peer dependency, causing module resolution
    errors when generating plugins outside a Backstage monorepo. This adds
    react-dom to peerDependencies (for consuming apps) and devDependencies
    (for local development). react-router-dom is also added to peerDependencies (for consuming apps) and devDependencies
    to support routing during plugin development.

    Fixes:

    • Module not found: Can't resolve 'react-dom'
    • Module not found: Can't resolve 'react-router-dom'

  • 1226647: Updated dependency esbuild to ^0.27.0.

  • f89a074: Updated dependency @pmmmwh/react-refresh-webpack-plugin to ^0.6.0.

  • 2b81751: Updated dependency webpack to ~5.103.0.

  • fafd9e1: Fixed internal usage of yargs.

  • c8c2329: Add proxy configuration from env-vars to create-app tasks

  • 2bae83a: Switched compilation target to ES2022 in order to match the new set of supported Node.js versions, which are 22 and 24.

    The TypeScript compilation target has been set to ES2022, because setting it to a higher target will break projects on older TypeScript versions. If you use a newer TypeScript version in your own project, you can bump compilerOptions.target to ES2023 or ES2024 in your own tsconfig.json file.

  • 7fbac5c: Updated to use new utilities from @backstage/cli-common.

  • 2bae83a: Bumped dev dependencies @types/node

  • Updated dependencies

backstage/backstage (@​backstage/plugin-api-docs)

v0.13.3

Compare Source

Patch Changes

v0.13.2

Compare Source

Patch Changes

v0.13.1

Compare Source

Patch Changes

v0.13.0

Compare Source

Minor Changes

  • b8a381e: Remove explicit dependency on isomorphic-form-data.

    This explicit dependency was added to address an issue in the
    dependency swagger-ui-react. That issue has since been resolved,
    and isomorphic-form-data no longer needs to be declared.

    Additionally, this changeset updates the swagger-ui-react dependency to version 5.19.0 or higher, which includes
    compatibility with the latest versions of
    the OpenAPI specification.

Patch Changes
backstage/backstage (@​backstage/plugin-auth-backend)

v0.26.0

Compare Source

Minor Changes
  • 7ffc873: Fix user_created_at migration causing SQLiteError regarding use of non-constants for defaults
Patch Changes
backstage/backstage (@​backstage/plugin-scaffolder-node)

v0.12.3

Compare Source

Patch Changes

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

Patch Changes

v0.12.0

Compare Source

Minor Changes

  • 9b81a90: BREAKING - Marking optional fields as required in the TaskBroker, these can be fixed with a no-op () => void if you don't want to implement the functions.

    • cancel, recoverTasks and retry are the required methods on the TaskBroker interface.

    NOTE: If you're affected by this breaking change, please reach out to us in an issue as we're thinking about completely removing the TaskBroker extension point soon and would like to hear your use cases for the upcoming re-architecture of the scaffolder-backend plugin.

Patch Changes

  • c8aa210: BREAKING ALPHA: We've moved the scaffolderActionsExtensionPoint from /alpha to the main export.

    // before
import { scaffolderActionsExtensionPoint } from '@​backstage/plugin-scaffolder-node/alpha';

// after
import { scaffolderActionsExtensionPoint } from '@​backstage/plugin-scaffolder-node';

  • 6e2bda7: DEPRECATION: We're going to be working on refactoring a lot of the internals of the Scaffolder backend plugin, and with that comes a lot of deprecations and removals for public types that are making these things hard.

    If you're using these types, please reach out to us either on Discord or a GitHub issue with your use cases.

    • SerializedTask, SerializedTaskEvent, TaskBroker, TaskContext, TaskBrokerDispatchOptions, TaskBrokerDispatchResult, TaskCompletionState, TaskEventType, TaskFilter, TaskFilters, TaskStatus are the types that have now been marked as deprecated, and will be removed in a future release.

  • Updated dependencies

backstage/backstage (@​backstage/theme)

v0.7.1

Compare Source

Patch Changes
  • fa06f6b: Added a themeName prop to UnifiedThemeProvider, enabling Backstage UI data-theme-name CSS attribute to be set based on active theme.

v0.7.0

Compare Source

Minor Changes

  • 865bce8: BREAKING: Removed the built-in CssBaseline from UnifiedThemeProvider. If your Backstage instance looks broken after this update, you likely forgot to add our new Backstage UI global CSS. To do that, please import @backstage/ui/css/styles.css in packages/app/src/index.tsx:

    import '@​backstage/ui/css/styles.css';

    This change also removes the noCssBaseline prop, which became redundant.

Patch Changes
  • d5cbdba: The UnifiedThemeProvider now coordinates theme attributes on the document body in case multiple theme providers are rendered.
brianc/node-postgres (pg)

v8.17.2

Compare Source

v8.17.1

Compare Source

v8.17.0

Compare Source

  • Throw correct error if database URL parsing fails.
yarnpkg/berry (yarn)

v4.12.0

Compare Source

v4.11.0

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner October 20, 2025 09:59
@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from 94407cf to d5b8b95 Compare October 24, 2025 18:59
@renovate renovate bot force-pushed the renovate/all-minor branch from d5b8b95 to 3c1363d Compare October 29, 2025 12:26
@renovate renovate bot force-pushed the renovate/all-minor branch 4 times, most recently from 75eb12a to 07a8f2b Compare November 16, 2025 06:31
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from 6fd0fb5 to 943f1fb Compare November 21, 2025 22:55
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from 7173e6d to f56c035 Compare November 30, 2025 13:04
@renovate renovate bot force-pushed the renovate/all-minor branch 3 times, most recently from 7b12289 to 0b508b7 Compare December 8, 2025 19:29
@renovate renovate bot force-pushed the renovate/all-minor branch from 0b508b7 to c65be5e Compare December 14, 2025 10:29
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from dcdb448 to f90bf83 Compare December 25, 2025 13:06
@renovate renovate bot force-pushed the renovate/all-minor branch 5 times, most recently from dc190ff to b8be967 Compare January 7, 2026 12:28
@renovate renovate bot force-pushed the renovate/all-minor branch from b8be967 to 04e6a2a Compare January 8, 2026 17:16
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from ce4f430 to 686d4ed Compare January 21, 2026 17:27
@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from 748f19b to df1127c Compare January 28, 2026 11:03
@renovate renovate bot force-pushed the renovate/all-minor branch from df1127c to 15328fe Compare January 28, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants