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

fix(deps): update backstage monorepo #49

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

fix(deps): update backstage monorepo #49

wants to merge 1 commit into from
+8 −18

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 6, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@backstage/cli (source) ^0.26.0 -> ^0.29.0 age adoption passing confidence
@backstage/core-app-api (source) 1.14.2 -> 1.15.4 age adoption passing confidence
@backstage/core-components (source) ^0.14.3 -> ^0.16.0 age adoption passing confidence
@backstage/core-plugin-api (source) 1.9.3 -> 1.10.3 age adoption passing confidence
@backstage/dev-utils (source) 1.0.37 -> 1.1.6 age adoption passing confidence
@backstage/plugin-catalog-react (source) 1.12.3 -> 1.15.1 age adoption passing confidence
@backstage/test-utils (source) 1.5.10 -> 1.7.4 age adoption passing confidence
@backstage/theme (source) ^0.5.2 -> ^0.6.0 age adoption passing confidence

Release Notes

backstage/backstage (@​backstage/cli)

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

v0.28.2

Compare Source

v0.28.1

Compare Source

v0.28.0

Compare Source

Minor Changes

  • 264058c: The repo test command will no longer default to watch mode if the --since flag is provided.

  • 55b8b84: BREAKING: The Jest configuration defined at @backstage/cli/config/jest no longer collects configuration defined in the "jest" field from all parent package.json files. Instead, it will only read and merge configuration from the package.json in the monorepo root if it exists, as well as the target package. In addition, configuration defined in the root package.json will now only be merged into each package configuration if it is a valid project-level configuration key.

  • 6129076: BREAKING: Removed the following deprecated commands:

    • create: Use backstage-cli new instead
    • create-plugin: Use backstage-cli new instead
    • plugin:diff: Use backstage-cli fix instead
    • test: Use backstage-cli repo test or backstage-cli package test instead
    • versions:check: Use yarn dedupe or yarn-deduplicate instead
    • clean: Use backstage-cli package clean instead

    In addition, the experimental install and onboard commands have been removed since they have not received any updates since their introduction and we're expecting usage to be low. If you where relying on these commands, please let us know by opening an issue towards the main Backstage repository.

Patch Changes

  • ea16633: Preserve directory structure for CommonJS build output, just like ESM. This makes the build output more stable and easier to browse, and allows for more effective tree shaking and lazy imports.

  • 520a383: Added functionality to the prepack script that will append the default export type for entry points to the exports object before publishing. This is to help with identifying the declarative integration points for plugins without needing to fetch or run the plugins first.

  • 9625a97: The scaffolder-module template has been updated to use a more modern layout and new testing utilities for scaffolder actions.

  • 03810d2: Remove unknown dependency diff

  • cebee4f: Added support for a new experimental EXPERIMENTAL_TRIM_NEXT_ENTRY flag which removes any ./next entry points present in packages when building and publishing.

  • 54c8aa3: The check for react-dom/client will now properly always run from the target directory.

  • b676cc9: feat: experimentally support using rspack instead under EXPERIMENTAL_RSPACK env flag

  • 094eaa3: Remove references to in-repo backend-common

  • 95999c5: The backend plugin template for the new command has been updated to provide more guidance and use a more modern structure.

  • 7955f9b: Tweaked the new package feature detection to not be active when building backend packages.

  • 4bfc2ce: Updated the Vite implementation behind the EXPERIMENTAL_VITE flag to work with more recent versions of Backstage.

  • 720a2f9: Updated dependency git-url-parse to ^15.0.0.

  • 8f0898b: Updated dependency esbuild to ^0.24.0.

  • 2c5ecf5: Support --max-warnings flag for package linting

  • 88407c3: Running repo lint with the --successCache flag now respects .gitinore, and it ignores projects without a lint script.

  • 8fe740d: Added a new --successCache option to the backstage-cli repo test and backstage-cli repo lint commands. The cache keeps track of successful runs and avoids re-running for individual packages if they haven't changed. This option is intended only to be used in CI.

    In addition a --successCacheDir <path> option has also been added to be able to override the default cache directory.

  • 55b8b84: The Jest configuration will now search for a src/setupTests.* file with any valid script extension, not only .ts.

  • 79ba5a8: The LEGACY_BACKEND_START flag is now deprecated.

  • f0514c7: Disabled parsing of input source maps in the SWC transform for Jest.

  • Updated dependencies

v0.27.1

Compare Source

Patch Changes

  • d2d2313: Add config.d.ts files to the list of included file in tsconfig.json.

    This allows ESLint to detect issues or deprecations in those files.

  • 16ffdd6: Remove direct vite dependency

  • 8069f4a: Update Scaffolder module template to add itself to the backend

  • 97422b0: Update templates to not refer to backend-common

  • 0e1a817: The app build process now outputs an additional index.html.tmpl file. This is an non-templated version of the index.html file, which can be used to delay templating until runtime.

    The new index.html.tmpl file also sets a backstage-public-path meta tag to be templated at runtime. The meta tag is in turn picked up by the new @backstage/cli/config/webpack-public-path.js entry point script, which uses it to set the runtime public path of the Webpack bundle.

  • 1b5c264: Add checks: 'read' for default GitHub app permissions

  • b4685e7: Added watchOptions to frontend webpack config for compatibility with Yarn PnP

  • d29fc1b: Updated dependency @module-federation/enhanced to ^0.6.0.

  • f865103: Updated dependency esbuild to ^0.23.0.

  • ab7713a: Updated dependency eslint-plugin-jest to ^28.0.0.

  • c78ff91: Updated dependency @rollup/plugin-commonjs to ^26.0.0.

  • 4ebf36f: Upgrade to vite@v5

  • 2d3caaf: The build commands now support the new backstage.inline flag in package.json, which causes the contents of private packages to be inlined into the consuming package, rather than be treated as an external dependency.

  • 569c3f0: Fixed an issue where published frontend packages would end up with an invalid import structure if a single module imported both .css and .svg files.

  • 3d88455: Add support for backstage:^ version ranges to versions:bump when using the experimental yarn plugin

  • d10f6b6: Allow overriding minify flag with build repo command

  • Updated dependencies

v0.27.0

Compare Source

Minor Changes

  • 32a38e1: BREAKING: The lockfile (yarn.lock) dependency analysis and mutations have been removed from several commands.

    The versions:bump command will no longer attempt to bump and deduplicate dependencies by modifying the lockfile, it will only update package.json files.

    The versions:check command has been removed, since its only purpose was verification and mutation of the lockfile. We recommend using the yarn dedupe command instead, or the yarn-deduplicate package if you're using Yarn classic.

    The check that was built into the package start command has been removed, it will no longer warn about lockfile mismatches.

    The packages in the Backstage ecosystem handle package duplications much better now than when these CLI features were first introduced, so the need for these features has diminished. By removing them, we drastically reduce the integration between the Backstage CLI and Yarn, making it much easier to add support for other package managers in the future.

Patch Changes
backstage/backstage (@​backstage/core-app-api)

v1.15.4

Compare Source

Patch Changes

v1.15.3

Compare Source

Patch Changes
  • e5fa018: The OAuth 2 client implementations will now attempt to refresh the session when the existing session doesn't have the required scopes. The previous behavior was to only try to refresh the session of it was missing, and otherwise directly request a new session. This fixes an issue where some auth providers will not return access tokens with certain scopes unless explicitly requested, leading to an auth popup even if the underlying session already had been granted the requested scopes.
  • 2830689: Decrease OAuth2 token refresh grace period
  • Updated dependencies

v1.15.2

Compare Source

Patch Changes

v1.15.1

Compare Source

Patch Changes

v1.15.0

Compare Source

Minor Changes
  • ddbeace: Added the ability to explicitly disable routes through the bindRoutes option by passing false as the route target. This also fixes a bug where route bindings in config were incorrectly prioritized above the ones in code in certain situations.
Patch Changes
backstage/backstage (@​backstage/core-components)

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

v0.15.1

Compare Source

Patch Changes

v0.15.0

Compare Source

Minor Changes

  • 9adc552: Added missing items to overridableComponents

    BREAKING Overridable component name for styling OAuthRequestDialog changed to BackstageOAuthRequestDialog. Overridable component name BackstageMissingAnnotationEmptyState that was previously deprecated has been removed.

Patch Changes
backstage/backstage (@​backstage/core-plugin-api)

[v1.10.3](https://redirect.github.com/backstag

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • 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 added the dependencies Pull requests that update a dependency file label Feb 6, 2025
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
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants