Skip to content
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

chore: Update all minor dependency updates #159

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

chore: Update all minor dependency updates #159

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 28, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@backstage-community/plugin-github-actions (source) ^0.6.16 -> ^0.7.0 age adoption passing confidence
@backstage/backend-defaults (source) ^0.5.0 -> ^0.6.0 age adoption passing confidence
@backstage/catalog-client (source) 1.7.1 -> 1.9.0 age adoption passing confidence
@backstage/cli (source) ^0.28.0 -> ^0.29.0 age adoption passing confidence
@backstage/config (source) 1.2.0 -> 1.3.1 age adoption passing confidence
@backstage/core-components (source) ^0.15.0 -> ^0.16.0 age adoption passing confidence
@backstage/plugin-api-docs (source) ^0.11.5 -> ^0.12.0 age adoption passing confidence
@backstage/plugin-app-backend (source) ^0.3.67 -> ^0.4.0 age adoption passing confidence
@backstage/plugin-auth-backend (source) ^0.23.0 -> ^0.24.0 age adoption passing confidence
@backstage/plugin-catalog (source) 1.24.0 -> 1.26.0 age adoption passing confidence
@backstage/plugin-catalog-backend (source) 1.27.1 -> 1.29.0 age adoption passing confidence
@backstage/plugin-catalog-react (source) 1.14.0 -> 1.15.0 age adoption passing confidence
@backstage/plugin-scaffolder (source) 1.26.2 -> 1.27.3 age adoption passing confidence
@backstage/plugin-scaffolder-backend (source) 1.26.2 -> 1.28.0 age adoption passing confidence
@backstage/plugin-search-backend (source) 1.6.1 -> 1.8.0 age adoption passing confidence
@backstage/plugin-techdocs (source) 1.11.0 -> 1.12.0 age adoption passing confidence
@commitlint/cli (source) 19.5.0 -> 19.6.1 age adoption passing confidence
@commitlint/config-conventional (source) 19.5.0 -> 19.6.0 age adoption passing confidence
msw (source) 2.6.4 -> 2.7.0 age adoption passing confidence
node-gyp 10.2.0 -> 10.3.1 age adoption passing confidence
react-use 17.5.1 -> 17.6.0 age adoption passing confidence
typescript (source) ~5.6.0 -> ~5.7.0 age adoption passing confidence
zod (source) 3.23.8 -> 3.24.1 age adoption passing confidence

Release Notes

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

v0.7.0

Compare Source

Minor Changes
  • 73c104f: Backstage version bump to v1.34.1

v0.6.27

Compare Source

Patch Changes
  • ede35ca: Use a consistent empty state in the workflow runs card regardless of the reason
    for the card being empty.

v0.6.26

Compare Source

Patch Changes
  • a130288: Truncate commit message to first newline

v0.6.25

Compare Source

Patch Changes
  • e657f8d: Add default filtering based on required annotation to the new frontend system components

v0.6.24

Compare Source

Patch Changes
  • 9501620: Updating README to include missing steps

v0.6.23

Compare Source

Patch Changes
  • 6fdae83: Backstage version bump to v1.32.0

v0.6.22

Compare Source

Patch Changes
  • 45fd620: use new FE system syntax (replacing deprecated methods)
  • 59b34f5: Backstage version bump to v1.30.2

v0.6.21

Compare Source

Patch Changes
  • a0591d5: Make entity cards/content appear on Components only by default in new FE system

v0.6.20

Compare Source

Patch Changes
  • 8711599: Updating readmes in github actions to add configuration steps and removed incorrect limitations
backstage/backstage (@​backstage/backend-defaults)

v0.6.2

Compare Source

v0.6.1

Compare Source

v0.6.0

Compare Source

Minor Changes

  • fd5d337: Added a new backend.health.headers configuration that can be used to set additional headers to include in health check responses.

    BREAKING CONSUMERS: As part of this change the createHealthRouter function exported from @backstage/backend-defaults/rootHttpRouter now requires the root config service to be passed through the config option.

  • 3f34ea9: Throttles Bitbucket Server API calls

  • de6f280: BREAKING Upgraded @​keyv/redis and keyv packages to resolve a bug related to incorrect resolution of cache keys.

    This is a breaking change for clients using the redis store for cache with useRedisSets option set to false since cache keys will be calculated differently (without the sets:namespace: prefix). For clients with default configuration (or useRedisSets set to false) the cache keys will stay the same, but since @​keyv/redis library no longer supports redis sets they won't be utilised anymore.

    If you were using useRedisSets option in configuration make sure to remove it from app-config.yaml:

    backend:
  cache:
    store: redis
    connection: redis://user:[email protected]:6379
-   useRedisSets: false

  • 29180ec: BREAKING PRODUCERS: The LifecycleMiddlewareOptions.startupRequestPauseTimeout has been removed. Use the backend.lifecycle.startupRequestPauseTimeout setting in your app-config.yaml file to customize how the createLifecycleMiddleware function should behave. Also the root config service is required as an option when calling the createLifecycleMiddleware function:

    - createLifecycleMiddleware({ lifecycle, startupRequestPauseTimeout })
+ createLifecycleMiddleware({ config,  lifecycle })

  • 277092a: Implemented AzureBlobStorageUrlReader to read from the url of committed location from the entity provider

  • 18a2c00: All middleware used by the default coreServices.http is now exported for use by custom implementations.

Patch Changes

v0.5.3

Compare Source

Patch Changes

v0.5.2

Compare Source

v0.5.1

Compare Source

Patch Changes
backstage/backstage (@​backstage/catalog-client)

v1.9.0

Compare Source

Minor Changes
  • 384e494: Internal updates to generated code.
Patch Changes

v1.8.0

Compare Source

Minor Changes
  • 656d1ef: Internal update to use the updated generated code from backstage-cli package schema openapi generate --client-package ....
  • 31c4fe0: The client now automatically splits up very large getEntitiesByRefs calls into several smaller requests behind the scenes when needed. This ensures that each individual request does not exceed common Express.js request body limits or overload the server.
Patch Changes
backstage/backstage (@​backstage/cli)

v0.29.4

Compare Source

Patch Changes

v0.29.3

Compare Source

Patch Changes

v0.29.2

Compare Source

The @backstage/core package has been split into the following three packages, all published as part of this release.

Name Description
@backstage/core-app-api Core app API used by Backstage apps
@backstage/core-plugin-api Core API used by Backstage plugins and apps
@backstage/core-components Core components used by Backstage plugins and apps

The main purpose of the split is to decouple the plugin API versioning from the app. It is now possible to bring in multiple plugins that depend on different versions of the core API, without any significant overhead.

The existing @backstage/core package still works together with these new packages, meaning that there is no rush to migrate, and we do not recommend that projects are migrated just yet. In general migration will be done by simply replacing usages of @backstage/core with either @backstage/core-plugin-api, @backstage/core-app-api, or @backstage/core-components, depending on what's being imported, but more information will follow!

v0.29.1

Compare Source

Published a new @backstage/backend-test-utils package, which is a package for backend test utilities.

v0.29.0

Compare Source

Minor Changes

  • bc47b17: BREAKING: Updates ESLint config to ignore all generated source code under src/**/generated/**/*.ts.

  • 6819f8c: Added a new optimization to the repo test command that will filter out unused packages in watch mode if all provide filters are paths that point from the repo root. This significantly speeds up running individual tests from the repo root in a large workspace, for example:

    yarn test packages/app/src/App.test.tsx

  • d849865: The package packing now populates typesVersions for additional entry points rather than using additional package.json files for type resolution. This improves auto completion of separate entry points when consuming published packages.

  • bc71665: BREAKING: The LEGACY_BACKEND_START flag has been removed, along with support for src/run.ts as the development entry point.

Patch Changes

  • 4046d53: Fixed an issue where the --successCache option for the repo test and repo lint commands would be include the workspace path in generated cache keys. This previously broke caching in environments where the workspace path varies across builds.

  • 4a378d3: Fix dev server reloads of plugin discovery for new frontend system.

  • 28b60ad: The check for react-dom/client in the Jest configuration will now properly always run from the target directory.

  • 6b2888c: Fixed an issue with the --successCache flag for repo test where the tree hash for the wrong package directory would sometimes be used to generate the cache key.

  • e30b65d: Added --alwaysPack as a replacement for the now hidden --alwaysYarnPack flag for the build-workspace command.

  • be0278e: Removed circular import

  • a7f97e4: Added a new "rejectFrontendNetworkRequests" configuration flag that can be set in the "jest" field in the root package.json:

    {
  "jest": {
    "rejectFrontendNetworkRequests": true
  }
}

    This flag causes rejection of any form of network requests that are attempted to be made in frontend or common package tests. This flag can only be set in the root package.json and can not be overridden in individual package configurations.

  • 6c48ebd: Add --max-warnings -1 support to backstage-cli package lint

  • 04297a0: The --successCache option for the repo test and repo lint commands now use an additive store that keeps old entries around for a week before they are cleaned up automatically.

  • a2f0559: When using the experimental Rspack flag the app build and dev server now injects configuration via a <script type="backstage.io/config">...</script> tag in index.html rather than the process.env.APP_CONFIG definition, which will now be defined as an empty array instead.

    This requires the app to be using the config loader from the 1.31 release of Backstage. Make sure your app is using at least that version if you are upgrading to this version of the CLI.

    If you have copied the implementation of the defaultConfigLoader, make sure to update it to the new implementation. In particular the config loader needs to be able to read configuration from script tags with the type backstage.io/config.

  • b4627f2: Fixed an issue where the raw-loader for loading HTML templates was not resolved from the context of the CLI package.

  • cd1ef2b: Updated dependency vite to ^5.0.0.

  • 23f1da2: Updated dependency ts-morph to ^24.0.0.

  • b533056: Updated dependency css-loader to ^7.0.0.

  • be008c3: Updated dependency @module-federation/enhanced to ^0.7.0.

  • 6266ed3: Updated dependency del to ^8.0.0.

  • 4046d53: Fixed an issue with the repo lint command where the cache key for the --successCache option would not properly ignore files that should be ignored according to .eslintignores.

  • e19c53c: Fix for the --link flag for package start to deduplicate react-router and react-router-dom.

  • 17850a5: Update upgrade-helper link in versions:bump command to include yarnPlugin parameter when the yarn plugin is installed

  • 09ea093: Fixed an issue where .css style injection would fail for published packages.

  • 702f41d: Bumped dev dependencies @types/node

  • 5d74716: Remove unused backend-common dependency

  • b084f5a: Bump the Webpack dependency range to ^5.94.0, as our current configuration is not compatible with some older versions.

  • e565f73: Added support for .webp files in the frontend tooling.

  • 946fa34: Added a new --link <workspace-path> option for frontend builds that allow you to override module resolution to link in an external workspace at runtime.

    As part of this change the Webpack linked workspace resolution plugin for frontend builds has been removed. It was in place to support the old workspace linking where it was done by Yarn, which is no longer a working option.

  • Updated dependencies

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 November 28, 2024 08:24
@renovate renovate bot force-pushed the renovate/all-minor branch 5 times, most recently from 5898ce4 to d7a68d6 Compare December 2, 2024 08:36
@renovate renovate bot force-pushed the renovate/all-minor branch from d7a68d6 to 0133231 Compare December 9, 2024 21:52
Kirdock
Kirdock previously approved these changes Dec 11, 2024
View reviewed changes
@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from f75c9f7 to 72494f0 Compare December 22, 2024 16:40
@renovate renovate bot force-pushed the renovate/all-minor branch 4 times, most recently from 8e2f3e9 to 7b61fb0 Compare December 31, 2024 00:58
@renovate renovate bot force-pushed the renovate/all-minor branch from 7b61fb0 to fda2ec8 Compare December 31, 2024 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Kirdock Kirdock Kirdock left review comments

At least 2 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Kirdock