feat(extensions-schema): allow production support level for plugin metadata by polasudo · Pull Request #2407 · redhat-developer/rhdh-plugins

polasudo · 2026-02-27T11:17:16Z

Jira: https://issues.redhat.com/browse/RHIDP-12372

User description

Summary

add production to the allowed enum values for spec.support.level in workspaces/extensions/json-schema/plugins.json
keep existing allowed values unchanged for backward compatibility

Why

Overlays metadata is being normalized to use production consistently. This schema update ensures plugin metadata validates correctly when that value is used.

Test plan

schema includes production in support.level enum
existing values (generally-available, tech-preview, dev-preview, community, none) remain supported

Made with Cursor

PR Type

Enhancement

Description

Add production to allowed enum values for spec.support.level
Enables plugin metadata to use production support level consistently
Maintains backward compatibility with existing support level values

Diagram Walkthrough

flowchart LR
  schema["plugins.json schema"] -- "add production enum value" --> support["support.level enum"]
  support -- "includes" --> values["production, generally-available, tech-preview, dev-preview, community, none"]

File Walkthrough

Relevant files

Enhancement

plugins.json `Add production to support level enum` workspaces/extensions/json-schema/plugins.json Added `production` to the `spec.support.level` enum values Positioned as first enum value in the list All existing support level values remain unchanged and supported	+1/-0

…tadata Add `production` to the allowed values for `spec.support.level` in the extensions plugins schema so downstream metadata can consistently use production without schema validation errors. Made-with: Cursor

rhdh-qodo-merge · 2026-02-27T11:17:35Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
🟢	No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

rhdh-qodo-merge · 2026-02-27T11:18:30Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ ~~Clarify potentially confusing enum values~~ Suggestion Impact: Instead of adding a descriptive text to clarify the enum values, the commit removed the "generally-available" enum option from the schema, reducing the ambiguity the suggestion called out but not implementing the proposed description field. code diff: @@ -129,7 +129,6 @@ "type": "string", "enum": [ "production", - "generally-available", "tech-preview", "dev-preview", "community", Add a `description` field to the `level` property in the JSON schema to clarify the meaning of each support level, especially the distinction between `production` and `generally-available`. workspaces/extensions/json-schema/plugins.json [128-135] "level": { "type": "string", + "description": "Defines the support level of the plugin. 'production' is for fully supported, production-ready plugins. 'generally-available' is for stable releases that are not yet at full production support. 'tech-preview' and 'dev-preview' are for pre-release versions. 'community' is for community-supported plugins.", "enum": [ "production", "generally-available", "tech-preview", "dev-preview", "community", ... `[To ensure code accuracy, apply this suggestion manually]` Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that the terms `production` and `generally-available` can be ambiguous and proposes adding a `description` to the JSON schema, which is a good practice for clarity and usability.	Low
Update

workspaces/extensions/json-schema/plugins.json

…uction Remove remaining generally-available usage across extensions schema, types, examples, docs, and e2e references so production is the single support-level term used consistently. Made-with: Cursor

rhdh-gh-app · 2026-02-27T12:50:18Z

Important

This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior.

Missing Changesets

The following package(s) are changed by this PR but do not have a changeset:

@red-hat-developer-hub/backstage-plugin-extensions

See CONTRIBUTING.md for more information about how to add changesets.

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
@red-hat-developer-hub/backstage-plugin-extensions-common	workspaces/extensions/plugins/extensions-common	minor	`v0.14.4`
@red-hat-developer-hub/backstage-plugin-extensions	workspaces/extensions/plugins/extensions	none	`v0.14.4`

Add missing changeset for @red-hat-developer-hub/backstage-plugin-extensions-common so the PR includes the required version bump metadata. Made-with: Cursor

Replace outdated GENERALLY_AVAILABLE enum checks with PRODUCTION in extensions UI filtering and badge logic to match the renamed support level enum. Made-with: Cursor

Remove unused React runtime import and disable legacy react-in-jsx-scope lint rule for this file so TypeScript and lint checks both pass with modern JSX transform. Made-with: Cursor

Regenerate and commit API extractor report files after support-level and translation surface changes so API report checks pass in CI. Made-with: Cursor

The report was generated by build:api-reports internal compilation which produces a different key ordering than tsc:full. CI runs tsc:full first, then build:api-reports:only --ci, so the committed report must match the tsc:full declaration output ordering. Made-with: Cursor

dzemanov

Tested this works correctly:

workspaces/extensions/.changeset/few-bugs-teach.md

Record the production terminology migration as a breaking change for extensions-common and document migration guidance for generally-available metadata. Made-with: Cursor

Change support-level terminology from 'generally-available' to 'production' in various schemas and documentation.

dzemanov

/approve
/lgtm

Thank you!

christoph-jerolimov

I like to understand this (to me) ad hoc change of an API before we continue.

nickboldt · 2026-03-03T13:35:21Z

I like to understand this (to me) ad hoc change of an API before we continue.

Well, to quote myself in RHIDP-12372:

we want to be consistent with the metadata, because obvious reasons.

If you would prefer to use generally-available everywhere instead of production, I'm fine with that. The point was to be CONSISTENT, not to force an API change.

cc: @kim-tsao

openshift-ci · 2026-03-03T13:35:30Z

New changes are detected. LGTM label has been removed.

sonarqubecloud · 2026-03-03T13:36:53Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

feat(extensions-schema): allow production support level for plugin me…

5dca8fe

…tadata Add `production` to the allowed values for `spec.support.level` in the extensions plugins schema so downstream metadata can consistently use production without schema validation errors. Made-with: Cursor

polasudo requested review from a team, christoph-jerolimov and karthikjeeyar as code owners February 27, 2026 11:17

rhdh-qodo-merge bot added the Review effort 1/5 label Feb 27, 2026

This was referenced Feb 27, 2026

chore(metadata): normalize support level terminology to production redhat-developer/rhdh-plugin-export-overlays#1978

Open

chore(metadata): normalize support level terminology to production redhat-developer/rhdh-plugin-export-overlays#1979

Open

nickboldt reviewed Feb 27, 2026

View reviewed changes

workspaces/extensions/json-schema/plugins.json Outdated Show resolved Hide resolved

chore(extensions): replace generally-available support term with prod…

a4faa47

…uction Remove remaining generally-available usage across extensions schema, types, examples, docs, and e2e references so production is the single support-level term used consistently. Made-with: Cursor

polasudo added 5 commits February 27, 2026 14:05

chore(changeset): add extensions-common patch changeset

5ab72db

Add missing changeset for @red-hat-developer-hub/backstage-plugin-extensions-common so the PR includes the required version bump metadata. Made-with: Cursor

fix(extensions): update support-level enum references to production

b570e6d

Replace outdated GENERALLY_AVAILABLE enum checks with PRODUCTION in extensions UI filtering and badge logic to match the renamed support level enum. Made-with: Cursor

fix(extensions): resolve Badges.tsx React import tsc error

9ba53c2

Remove unused React runtime import and disable legacy react-in-jsx-scope lint rule for this file so TypeScript and lint checks both pass with modern JSX transform. Made-with: Cursor

chore(extensions): refresh generated API reports

4be82b3

Regenerate and commit API extractor report files after support-level and translation surface changes so API report checks pass in CI. Made-with: Cursor

dzemanov requested changes Mar 2, 2026

View reviewed changes

workspaces/extensions/.changeset/few-bugs-teach.md Outdated Show resolved Hide resolved

polasudo and others added 3 commits March 2, 2026 13:49

Merge branch 'main' into chore/allow-production-support-level

857dd1f

chore(changeset): mark extensions-common support-level update as major

01956df

Record the production terminology migration as a breaking change for extensions-common and document migration guidance for generally-available metadata. Made-with: Cursor

Normalize support-level terminology in extensions

5bcb2f9

Change support-level terminology from 'generally-available' to 'production' in various schemas and documentation.

dzemanov approved these changes Mar 2, 2026

View reviewed changes

openshift-ci bot assigned dzemanov Mar 2, 2026

openshift-ci bot added the lgtm label Mar 2, 2026

polasudo requested a review from nickboldt March 2, 2026 15:24

christoph-jerolimov requested changes Mar 3, 2026

View reviewed changes

Merge branch 'main' into chore/allow-production-support-level

b64efa6

openshift-ci bot removed the lgtm label Mar 3, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(extensions-schema): allow production support level for plugin metadata#2407

feat(extensions-schema): allow production support level for plugin metadata#2407
polasudo wants to merge 11 commits intoredhat-developer:mainfrom
polasudo:chore/allow-production-support-level

polasudo commented Feb 27, 2026 •

edited

Loading

Uh oh!

rhdh-qodo-merge bot commented Feb 27, 2026 •

edited

Loading

Uh oh!

rhdh-qodo-merge bot commented Feb 27, 2026 •

edited

Loading

Uh oh!

Uh oh!

rhdh-gh-app bot commented Feb 27, 2026 •

edited

Loading

Uh oh!

dzemanov left a comment

Uh oh!

Uh oh!

dzemanov left a comment

Uh oh!

christoph-jerolimov left a comment

Uh oh!

nickboldt commented Mar 3, 2026

Uh oh!

openshift-ci bot commented Mar 3, 2026

Uh oh!

sonarqubecloud bot commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

polasudo commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

Summary

Why

Test plan

PR Type

Description

Diagram Walkthrough

File Walkthrough

Uh oh!

rhdh-qodo-merge bot commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Compliance Guide 🔍

Uh oh!

rhdh-qodo-merge bot commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Code Suggestions ✨

Uh oh!

Uh oh!

rhdh-gh-app bot commented Feb 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Missing Changesets

Changed Packages

Uh oh!

dzemanov left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

dzemanov left a comment

Choose a reason for hiding this comment

Uh oh!

christoph-jerolimov left a comment

Choose a reason for hiding this comment

Uh oh!

nickboldt commented Mar 3, 2026

Uh oh!

openshift-ci bot commented Mar 3, 2026

Uh oh!

sonarqubecloud bot commented Mar 3, 2026

Quality Gate passed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

polasudo commented Feb 27, 2026 •

edited

Loading

rhdh-qodo-merge bot commented Feb 27, 2026 •

edited

Loading

rhdh-qodo-merge bot commented Feb 27, 2026 •

edited

Loading

rhdh-gh-app bot commented Feb 27, 2026 •

edited

Loading