Skip to content

Conversation

@logonoff
Copy link
Member

@logonoff logonoff commented Feb 11, 2026

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 11, 2026

@logonoff: This pull request references CONSOLE-5063 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@logonoff logonoff force-pushed the CONSOLE-5063-s3e7-branch-closing branch 2 times, most recently from c549689 to a5a76ad Compare February 11, 2026 14:46
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 11, 2026

@logonoff: This pull request references CONSOLE-5063 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

  • useReduxStore removed, reverted fallback redux store creation added in enable redux store context in SDK from app host #10448
  • coFetch-related code moved entirely to dynamic-plugin-sdk package
  • utilsConfig removed, reverted coFetch sourcing via dependency injection added in Convert coFetch utilities to typescript and move to plugin SDK #9660
  • auth.js converted to TypeScript
  • Removed AppInitSDK
  • We now update SDK storeHandler object directly after initializing our redux store
  • initConsolePlugins now called directly after initializing PluginStore (speeding up loading times slightly)
  • initApiDiscovery moved outside the render function

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from jhadvig and rhamilto February 11, 2026 14:48
@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff

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:

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

@openshift-ci openshift-ci bot added component/sdk Related to console-plugin-sdk approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff

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:

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

@logonoff
Copy link
Member Author

/label px-approved
/label docs-approved

@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 11, 2026

@logonoff: This pull request references CONSOLE-5063 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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 openshift-eng/jira-lifecycle-plugin repository.

@logonoff logonoff force-pushed the CONSOLE-5063-s3e7-branch-closing branch from a5a76ad to 4a8b11d Compare February 11, 2026 15:14
logoutURL,
} = window.SERVER_FLAGS;
// type cast to prevent missing properties errors when building with limited SDK types
} = (window.SERVER_FLAGS as unknown) as Record<string, string>;
Copy link
Contributor

Choose a reason for hiding this comment

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

I can look into this, maybe it's related to some other type issue.

@logonoff logonoff force-pushed the CONSOLE-5063-s3e7-branch-closing branch from 4a8b11d to 081f4a7 Compare February 12, 2026 13:48
@logonoff logonoff force-pushed the CONSOLE-5063-s3e7-branch-closing branch from 081f4a7 to 5043883 Compare February 12, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality component/sdk Related to console-plugin-sdk docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. px-approved Signifies that Product Support has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants