Skip to content

ROX-33772: Update immutable to 4.3.8#19964

Open
dvail wants to merge 1 commit intorelease-4.8from
dv/update-immutable-4.3.8___release-4.8
Open

ROX-33772: Update immutable to 4.3.8#19964
dvail wants to merge 1 commit intorelease-4.8from
dv/update-immutable-4.3.8___release-4.8

Conversation

@dvail
Copy link
Copy Markdown
Contributor

@dvail dvail commented Apr 13, 2026

Description

Update optional peer dep immutable to the latest.

User-facing documentation

Testing and quality

  • the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
  • CI results are inspected

Automated testing

  • added unit tests
  • added e2e tests
  • added regression tests
  • added compatibility tests
  • modified existing tests

How I validated my change

change me!

@dvail dvail requested a review from a team as a code owner April 13, 2026 15:51
@github-actions github-actions bot added area/ui backport PR to backport changes from master to release branch labels Apr 13, 2026
@rhacs-bot
Copy link
Copy Markdown
Contributor

Images are ready for the commit at 658ab8b.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.8.10-3-g658ab8b217.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.73%. Comparing base (5149581) to head (658ab8b).

Additional details and impacted files
@@             Coverage Diff              @@
##           release-4.8   #19964   +/-   ##
============================================
  Coverage        48.73%   48.73%           
============================================
  Files             2595     2595           
  Lines           190828   190828           
============================================
+ Hits             93002    93004    +2     
+ Misses           90513    90512    -1     
+ Partials          7313     7312    -1     
Flag Coverage Δ
go-unit-tests 48.73% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Copy Markdown
Contributor

/konflux-retest operator-bundle-on-push

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

/konflux-retest operator-bundle-on-push

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 13, 2026

@dvail: 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/ocp-4-12-ui-e2e-tests 658ab8b link false /test ocp-4-12-ui-e2e-tests
ci/prow/ocp-dev-preview-ui-e2e-tests 658ab8b link false /test ocp-dev-preview-ui-e2e-tests
ci/prow/ocp-next-candidate-ui-e2e-tests 658ab8b link false /test ocp-next-candidate-ui-e2e-tests
ci/prow/ocp-4-20-ui-e2e-tests 658ab8b link false /test ocp-4-20-ui-e2e-tests

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.

"version": "4.0.0",
"resolved": "https://registry.npmjs.org/immutable/-/immutable-4.0.0.tgz",
"integrity": "sha1-uG943mre82CDle+yaakUYnl+LCM= sha512-zIE9hX70qew5qTUjSS7wi1iwj/l7+m54KWU247nhM3v806UdGj1yDndXj+IOYxxtW9zyLI+xqFNZjTuDaLUqFw==",
"version": "4.3.8",
Copy link
Copy Markdown
Contributor

@pedrottimark pedrottimark Apr 13, 2026

Choose a reason for hiding this comment

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

@dvail Is 4.3.8 the intended change for 4.8 release branch?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yeah, this was the automatic "latest version" that was resolved by npm. Different from the 4.9 and 4.10 branches because those branches have a dependency on immutable ^3.x.

It does seem odd that this branch, while older, gets the newer version of the dependency. What do you think? Keep it in line with the 4.9 and 4.10 branches? Or downgrade from 4.0.0 to 3.8.3 here?

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

Labels

area/ui backport PR to backport changes from master to release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants