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 #178

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

chore: Update all minor dependency updates #178

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 25, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@backstage-community/plugin-github-actions (source) ^0.7.0 -> ^0.8.0 age adoption passing confidence
@backstage/cli (source) ^0.28.2 -> ^0.30.0 age adoption passing confidence
@backstage/core-components (source) ^0.15.1 -> ^0.16.0 age adoption passing confidence
@backstage/plugin-api-docs (source) ^0.11.11 -> ^0.12.0 age adoption passing confidence
@backstage/plugin-app-backend (source) ^0.3.76 -> ^0.4.0 age adoption passing confidence
@backstage/plugin-auth-backend (source) ^0.23.1 -> ^0.24.0 age adoption passing confidence
@backstage/plugin-auth-node (source) ^0.5.3 -> ^0.6.0 age adoption passing confidence
@commitlint/cli (source) 19.6.1 -> 19.7.1 age adoption passing confidence
@commitlint/config-conventional (source) 19.6.0 -> 19.7.1 age adoption passing confidence
lerna (source) 8.1.7 -> 8.2.0 age adoption passing confidence
react-router (source) 6.28.0 -> 6.29.0 age adoption passing confidence
react-router-dom (source) 6.28.0 -> 6.29.0 age adoption passing confidence

Release Notes

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

v0.8.0

Compare Source

Minor Changes
  • 435f142: Backstage version bump to v1.36.0

v0.7.2

Compare Source

Patch Changes
  • 58d4734: Fixed plugin setup documentation to show example of use with availability check in the catalog EntityPage
backstage/backstage (@​backstage/cli)

v0.30.0

Compare Source

Minor Changes

  • cb76663: BREAKING: Add support for native ESM in Node.js code. This changes the behavior of dynamic import expressions in Node.js code. Typically this can be fixed by replacing import(...) with require(...), with an as typeof import(...) cast if needed for types. This is because dynamic imports will no longer be transformed to require(...) calls, but instead be left as-is. This in turn allows you to load ESM modules from CommonJS code using import(...).

    This change adds support for the following in Node.js packages, across type checking, package builds, runtime transforms and Jest tests:

    • Dynamic imports that load ESM modules from CommonJS code.
    • Both .mjs and .mts files as explicit ESM files, as well as .cjs and .cts as explicit CommonJS files.
    • Support for the "type": "module" field in package.json to indicate that the package is an ESM package.

    There are a few caveats to be aware of:

    • To enable support for native ESM in tests, you need to run the tests with the --experimental-vm-modules flag enabled, typically via NODE_OPTIONS='--experimental-vm-modules'.
    • Declaring a package as "type": "module" in package.json is supported, but in tests it will cause all local transitive dependencies to also be treated as ESM, regardless of whether they declare "type": "module" or not.
    • Node.js has an ESM interoperability layer with CommonJS that allows for imports from ESM to identify named exports in CommonJS packages. This interoperability layer is only enabled when importing packages with a .cts or .cjs extension. This is because the interoperability layer is not fully compatible with the NPM ecosystem, and would break package if it was enabled for .js files.
    • Dynamic imports of CommonJS packages will vary in shape depending on the runtime, i.e. test vs local development, etc. It is therefore recommended to avoid dynamic imports of CommonJS packages and instead use require, or to use the explicit CommonJS extensions as mentioned above. If you do need to dynamically import CommonJS packages, avoid using default exports, as the shape of them vary across different environments and you would otherwise need to manually unwrap the import based on the shape of the module object.

  • b30e788: The new command is now powered by a new template system that allows you to define your own templates in a declarative way, as well as import existing templates from external sources. See the CLI templates documentation for more information.

    The following flags for the new command have been deprecated and will be removed in a future release:

    • --license=<license>: Configure the global license instead.
    • --no-private: Configure the global private instead.
    • --baseVersion=<version>: Configure the global version instead.
    • --npmRegistry=<url>: Configure the global publishRegistry instead.
    • --scope=<scope>: Configure the global namePrefix and/or namePluginInfix instead.

    As part of this change the template IDs and their options have changed. The following backwards compatibility mappings for the --select and --option flags are enabled when using the default set of templates, but they will also be removed in the future:

    • --select=plugin is mapped to --select=frontend-plugin instead.
    • --option=id=<id> is mapped to --option=pluginId=<id> instead.
Patch Changes

v0.29.6

Compare Source

v0.29.5

Compare Source

Patch Changes

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

backstage/backstage (@​backstage/core-components)

v0.16.4

Compare Source

Patch Changes

v0.16.3

Compare Source

Patch Changes

v0.16.2

Compare Source

Patch Changes

v0.16.1

Compare Source

Added @backstage/plugin-bitrise to show bitrise.io builds and download build artifacts.

screenshot

v0.16.0

Compare Source

Minor Changes
  • dc409c5: The SupportButton component will now be hidden if no support config is specified in app-config
Patch Changes
backstage/backstage (@​backstage/plugin-api-docs)

v0.12.4

Compare Source

Patch Changes

v0.12.3

Compare Source

Patch Changes

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

v0.12.0

Compare Source

Minor Changes
  • 6836522: Added support for pagination in api-docs plugin - DefaultApiExplorerPage
Patch Changes
backstage/backstage (@​backstage/plugin-app-backend)

v0.4.5

Compare Source

Patch Changes

v0.4.4

Compare Source

Patch Changes

v0.4.3

Compare Source

Patch Changes

v0.4.2

Compare Source

@​backstage/create-app@​0.3.0

Minor Changes
  • 0101c7a: Add search plugin to default template for CLI created apps
Patch Changes

  • a8573e5: techdocs-backend: Simplified file, removing individual preparers and generators.
    techdocs-backend: UrlReader is now available to use in preparers.

    In your Backstage app, packages/backend/plugins/techdocs.ts file has now been simplified,
    to remove registering individual preparers and generators.

    Please update the file when upgrading the version of @backstage/plugin-techdocs-backend package.

    const preparers = await Preparers.fromConfig(config, {
  logger,
  reader,
});

const generators = await Generators.fromConfig(config, {
  logger,
});

const publisher = await Publisher.fromConfig(config, {
  logger,
  discovery,
});

    You should be able to remove unnecessary imports, and just do

    import {
  createRouter,
  Preparers,
  Generators,
  Publisher,
} from '@&#8203;backstage/plugin-techdocs-backend';

@​backstage/techdocs-common@​0.3.0

Minor Changes

  • a8573e5: techdocs-backend: Simplified file, removing individual preparers and generators.
    techdocs-backend: UrlReader is now available to use in preparers.

    In your Backstage app, packages/backend/plugins/techdocs.ts file has now been simplified,
    to remove registering individual preparers and generators.

    Please update the file when upgrading the version of @backstage/plugin-techdocs-backend package.

    const preparers = await Preparers.fromConfig(config, {
  logger,
  reader,
});

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 February 25, 2025 13:54
@renovate renovate bot force-pushed the renovate/all-minor branch 3 times, most recently from 772dfe9 to 7e4591d Compare February 26, 2025 19:09
@renovate renovate bot force-pushed the renovate/all-minor branch from 7e4591d to 39f6a02 Compare March 3, 2025 13:54
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