Skip to content

Conversation

@logonoff
Copy link
Member

@logonoff logonoff commented Nov 21, 2025

Closes #92

after:

image

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2025
@openshift-ci-robot
Copy link

@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

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
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2025
@openshift-ci-robot
Copy link

@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

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 a review from yapei November 21, 2025 16:36
@openshift-ci-robot
Copy link

@logonoff: This pull request references Jira Issue OCPBUGS-65887, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

after:

image

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 OCPBUGS-65887-deps branch 5 times, most recently from bb3f145 to 6c4adfd Compare November 21, 2025 17:14
@@ -1,5 +1,10 @@
{
"typescript.tsdk": "./node_modules/typescript/lib",
"editor.formatOnSave": false,
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this to be an explicit option?

Does setting editor.codeActionsOnSave cause editor.formatOnSave to be enabled by default?

Copy link
Member Author

@logonoff logonoff Nov 21, 2025

Choose a reason for hiding this comment

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

We should explicitly disable formatOnSave (even overriding user workspace preferences) because it has problems with our eslint config. codeActionsOnSave is run before formatOnSave, but the formatOnSave formatting is incorrect according to the linter. This is very annoying.

with this namespace as follows:

```tsx
conster Header: React.FC = () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

😆 conster sounds like a const but stronger

package.json Outdated
"@babel/preset-env": "^7.28.5",
"@cypress/webpack-preprocessor": "^7.0.2",
"@openshift-console/dynamic-plugin-sdk": "4.19.1",
"@openshift-console/dynamic-plugin-sdk-webpack": "4.19.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

Big update to Console plugin SDK packages 👍

},
"dependencies": {
"@console/pluginAPI": "*"
"@console/pluginAPI": "^4.19.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

This should encourage real world plugins to utilize the @console/pluginAPI dependency 👍

"jsx": "react-jsx",
"allowJs": true,
"strict": false,
"strict": true,
Copy link
Contributor

Choose a reason for hiding this comment

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

👍 for the switch to TS strict mode

@openshift-ci
Copy link

openshift-ci bot commented Nov 21, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: logonoff
Once this PR has been reviewed and has the lgtm label, please ask for approval from vojtechszocs. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

/retest

1 similar comment
@logonoff
Copy link
Member Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Dec 17, 2025

@logonoff: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/images 6075b34 link true /test images
ci/prow/e2e-aws-plugin-template 6075b34 link true /test e2e-aws-plugin-template

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

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

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dependencies for branch 4.20 are outdated

3 participants