chore(deps): update dependency @red-hat-developer-hub/cli to v2.1.1 - #5011
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
added
cost-management
dependencies
renovate
Bot
requested review from
a team,
Aurobinda55,
PreetiW,
asmasarw,
batzionb,
kgaikwad,
mareklibra,
r14chandra and
ydayagi
as code owners
September 28, 2026 10:28
renovate
Bot
added
dependencies
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5011 +/- ##
=======================================
Coverage 63.65% 63.65%
=======================================
Files 2705 2705
Lines 106578 106578
Branches 30005 30008 +3
=======================================
Hits 67843 67843
Misses 36905 36905
Partials 1830 1830
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/rhdh-cost-management-dependencies-(minor)
branch
6 times, most recently
from
September 28, 2026 15:51
d0e352e to
c81f72f
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/rhdh-cost-management-dependencies-(minor)
branch
from
September 28, 2026 18:45
c81f72f to
6bb7e13
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
2.0.8→2.1.1Release Notes
redhat-developer/rhdh-cli (@red-hat-developer-hub/cli)
v2.1.1Compare Source
Added
plugin dev: Newrhdh-cli plugin devcommand (start,update,restart,stop,logs,status) for exporting a dynamic plugin and managing its lifecycle against an existing RHDH Local checkout (RHIDP-16672, #215). Use--rhdh-local-dir <path>orRHDH_LOCAL_DIRto point at the checkout;--configureadds the CLI-managed config include on first use.plugin dev restartrestarts the RHDH service without re-deploying the plugin, useful when changing RHDH Local configuration.plugin dev logsaccepts--followto stream output continuously,--rhdhfor RHDH application logs, and--installerfor plugin installer logs.Fixed
plugin new: Generatedpackage.jsonnow always includes aversionfield (defaults to0.1.0). Upstream standalone templates omit it, butplugin exportandnpm packboth require a version to produce a valid package tarball.plugin export: Both backend and frontend export paths now validate thatpackage.jsoncontains aversionfield before invokingnpm pack, and emit a clear error instructing users to add one. Plugins without aversionfield would previously fail silently inside the RHDH Local installer container. Existing plugins that omitversionwill now fail at export time — add"version": "0.1.0"(or higher) to theirpackage.json.plugin export:ensureDiris now called before writing the config schema file, preventing failures when the parent directory does not exist.v2.1.0Compare Source
Added
plugin new: Addrhdh-cli plugin new <name>to create standalone, version-pinned frontend, backend, and catalog processor module dynamic plugin projects. The command renders portable template assets from the release-matched@backstage/cli-module-newpackage (0.1.6for RHDH 2.1 / Backstage 1.54.6). The RHDH adapter supplies standalonebackstage.json, Yarn Berry configuration, TypeScript configuration, RHDH export guidance, and dev harnesses. All@backstage/*direct dependencies are pinned from the target release manifest; transitive ranges remain upstream-managed (RHIDP-16671, RHIDP-16668, #202, #208).plugin new --template <name>: Select a generated project type using the upstream portable template name (frontend-plugin,backend-plugin,catalog-processor-module) as an alternative to--type. Only templates with end-to-end test coverage are accepted. Passing an unsupported template name produces a clear error listing the accepted values.plugin new --module-id <id>: Override the module identifier for module-type templates (e.g.catalog-processor-module). Defaults to the plugin name when omitted, preserving non-interactive behaviour.plugin new --plugin-package <name>: Set the generatedpackage.jsonnamefield. Validated against npm package name rules (lowercase, max 214 chars, no whitespace or special characters). Defaults to@internal/backstage-plugin-<name>.catalog,api,search,docs, andtemplatecommand groups for querying and managing RHDH through Backstage actions. These commands support human-readable and JSON output, multi-instance targeting, structured errors, and entity reference disambiguation (RHIDP-14129, #156).Changed
dist/, includingdist/remoteEntry.js. Removed the frontend export options--scalprum-config,--generate-scalprum-assets,--no-generate-scalprum-assets,--generate-module-federation-assets, and--no-generate-module-federation-assets. Frontend module-federation assets are now always generated duringplugin export. Frontend exports warn when legacydist-scalprum/,plugin-manifest.json, orscalprumpackage metadata is still present. The legacyplugin buildandplugin startcommands have been removed.dist-scalprum/plugin-manifest.jsonto use the standard module-federation output underdist/and NFS metadata inbackstage.features.dist-scalprumand related glob entries from frontend pluginfilesfields and clean any checked-in legacy output before exporting with rhdh-cli 2.1.0 (#182).plugin new(package name convention): The default generatedpackage.jsonnameno longer carries a type suffix. Previously, the RHDH-owned backend template appended-backend(producing@internal/backstage-plugin-<name>-backend) and the catalog processor module template appended a similar suffix; the upstream@backstage/cli-module-newtemplates use a flat@internal/backstage-plugin-<name>for all types. Scripts or CI configurations that reference the old type-suffixed name should update accordingly, or pass--plugin-package @internal/backstage-plugin-<name>-backendto restore the previous name.Fixed
plugin new: Add the missingjest-environment-jsdomdevelopment dependency to generated projects soyarn testruns successfully (#204).plugin new(frontend): Generated frontend plugin tests now pass under Node 18+ without modification. The upstream@backstage/cli-module-new0.1.6 template pinnedmsw@1.0.0, whosesetupServer()does not interceptglobalThis.fetchused by Backstage'sfetchApiRefin tests, causing the generatedTodoPagetest to time out. Three RHDH template overlay files patch the generated project: the test is updated to the MSW v2 API (http/HttpResponse);setupTests.tsexposes the Web API globals (TextEncoder,BroadcastChannel, etc.) missing from Jest 29 + jsdom; andpackage.jsongainsjest.testEnvironmentOptions.customExportConditionsso Jest 29 resolves MSW v2'smsw/nodepackage-exports subpath. These overlays will be removed when RHDH targets@backstage/cli-module-new0.1.7+ (Backstage 1.55.0).main, andnextcompatibility mappings to Backstage 1.54.6.Configuration
📅 Schedule: (UTC)
🚦 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.