Version bump to 1.0.12.

[sriroopar]

Summary by CodeRabbit

• Chores
  • Incremented version to 1.0.12.

[coderabbitai]

📝 Walkthrough

Walkthrough

Package version incremented from 1.0.11 to 1.0.12 across configuration and component files. The version field in package.json and the consolePlugin.version field were updated, along with the hard-coded plugin version display in the OverviewDetail component.

Changes

Cohort / File(s)	Summary
Version Configuration package.json	Updated version and consolePlugin.version fields from 1.0.11 to 1.0.12.
UI Component Display src/components/OverviewDetail.tsx	Updated hard-coded displayed plugin version string from 1.0.11 to 1.0.12.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, a bump, a number's dance,
From one-oh-one to two we prance,
The version rises, small but true,
Another release, shiny and new! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Version bump to 1.0.12' directly and concisely describes the main change: incrementing the version number in package.json and related files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/components/OverviewDetail.tsx (1)

3-4: Consider implementing dynamic version retrieval.

The TODO comment highlights a valid concern: maintaining the version in three separate locations (here and twice in package.json) creates a maintenance burden and risk of desynchronization. Each version bump requires manual updates across all locations.

Would you like me to help implement a solution to dynamically retrieve the version from package.json instead of hard-coding it? This would eliminate the need to manually update this file during version bumps.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/OverviewDetail.tsx` around lines 3 - 4, OverviewDetail
currently returns a hard-coded string "1.0.12"; change it to read the package
version dynamically by importing the package.json version or using a build-time
env var and render that value instead. Locate the OverviewDetail component and
replace the literal with the dynamic value (for example import { version } from
'.../package.json' if resolveJsonModule is enabled or read
process.env.REACT_APP_VERSION / process.env.npm_package_version set at build
time), ensure TypeScript config allows JSON imports or add a small wrapper
module that exports the version, and update OverviewDetail to render that
exported version so future bumps come from package.json automatically.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/components/OverviewDetail.tsx`:
- Around line 3-4: OverviewDetail currently returns a hard-coded string
"1.0.12"; change it to read the package version dynamically by importing the
package.json version or using a build-time env var and render that value
instead. Locate the OverviewDetail component and replace the literal with the
dynamic value (for example import { version } from '.../package.json' if
resolveJsonModule is enabled or read process.env.REACT_APP_VERSION /
process.env.npm_package_version set at build time), ensure TypeScript config
allows JSON imports or add a small wrapper module that exports the version, and
update OverviewDetail to render that exported version so future bumps come from
package.json automatically.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8cb6aeb4-a673-4833-b3e2-39f79ce65deb

📥 Commits

Reviewing files that changed from the base of the PR and between 9ce189c and a97166a.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json
• src/components/OverviewDetail.tsx

[kyoto]

/approve
/lgtm

[kyoto]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@kyoto: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyoto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [kyoto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-cherrypick-robot]

@kyoto: new pull request created: #1808

Details

In response to this:

/cherry-pick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.