Skip to content

RHIDP-12083: remove dev preview banner from github events module as it is TP from 1.9#1764

Merged
Gerry-Forde merged 7 commits intoredhat-developer:mainfrom
04kash:1.9/event-plugin-updates
Feb 18, 2026
Merged

RHIDP-12083: remove dev preview banner from github events module as it is TP from 1.9#1764
Gerry-Forde merged 7 commits intoredhat-developer:mainfrom
04kash:1.9/event-plugin-updates

Conversation

@04kash
Copy link
Copy Markdown
Member

@04kash 04kash commented Feb 8, 2026

Github Events Module has been promoted to TP for 1.9. We should remove the dev preview banner from it. (And possibly add a tech preview banner if we have one and do that for other TP plugins)

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): 1.9
Issue:
https://issues.redhat.com/browse/RHIDP-12083
Preview:

Signed-off-by: Kashish Mittal <kmittal@redhat.com>
@rhdh-bot
Copy link
Copy Markdown
Collaborator

rhdh-bot commented Feb 8, 2026

Signed-off-by: Kashish Mittal <kmittal@redhat.com>
Comment thread modules/dynamic-plugins/proc-configuring-events-module-for-github.adoc Outdated
Comment thread modules/dynamic-plugins/proc-configuring-events-module-for-github.adoc Outdated
@nickboldt
Copy link
Copy Markdown
Member

Simpler would be to use the floating tag

oci://registry.access.redhat.com/rhdh/backstage-plugin-events-backend-module-github:1.9

but tha'ts not the recommended approach as you might get a DIFFERENT plugin when airgapping than you expect, if we release an update and the tag moves to a new value.

Pinned digests are better, but require more complicated documentation processes:

  dynamicArtifact: "oci://registry.access.redhat.com/rhdh/backstage-plugin-events-backend-module-github@sha256:2c1ccc4fb01883dc4da1aa0c417d6e28d944c6ce941454ee41698f2c1812035c"

Comment thread modules/dynamic-plugins/proc-configuring-events-module-for-github.adoc Outdated
Copy link
Copy Markdown
Member

@nickboldt nickboldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as the plugin is no longer DP, the DP disclaimer no longer applies.

Do we need a TP one instead?

@04kash
Copy link
Copy Markdown
Member Author

04kash commented Feb 17, 2026

Do we need a TP one instead?

I was looking at the existing docs and couldn't find a banner specifically for TP. @pabel-rh @deerskindoll is there one you'd recommend for this?

@deerskindoll
Copy link
Copy Markdown
Member

Do we need a TP one instead?

I was looking at the existing docs and couldn't find a banner specifically for TP. @pabel-rh @deerskindoll is there one you'd recommend for this?

this is the template we use: https://redhat-documentation.github.io/supplementary-style-guide/#technology-preview-guidance

Signed-off-by: Kashish Mittal <kmittal@redhat.com>
@04kash
Copy link
Copy Markdown
Member Author

04kash commented Feb 17, 2026

Thanks @deerskindoll! I've made the changes

Copy link
Copy Markdown
Member

@Fortune-Ndlovu Fortune-Ndlovu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm we can always add the {{inherit}} later if needed

Signed-off-by: Kashish Mittal <kmittal@redhat.com>
@sonarqubecloud
Copy link
Copy Markdown

@Gerry-Forde
Copy link
Copy Markdown
Member

/cherry-pick release-1.9

@openshift-cherrypick-robot
Copy link
Copy Markdown
Contributor

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

Details

In response to this:

/cherry-pick release-1.9

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.

@Gerry-Forde Gerry-Forde merged commit dab830b into redhat-developer:main Feb 18, 2026
8 of 9 checks passed
@openshift-cherrypick-robot
Copy link
Copy Markdown
Contributor

@Gerry-Forde: new pull request created: #1811

Details

In response to this:

/cherry-pick release-1.9

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants