chore(deps): bump formik from 2.4.2 to 2.4.6 in /ui

[dependabot]

Bumps formik from 2.4.2 to 2.4.6.

Release notes

Sourced from formik's releases.

formik@2.4.6

Patch Changes

• f57ca9b #3949 Thanks @​DeveloperRaj! - Changing the state inside formik was changing reference of initialValues provided via props, deep cloning the initialvalues will fix it.

formik@2.4.5

Patch Changes

• d7db9cd #3860 Thanks @​patik! - Add missing dependency @types/hoist-non-react-statics, closes #3837

• fe4ed7e #3501 Thanks @​markspolakovs! - Mark formik as side-effect free in package.json

formik@2.4.4

Patch Changes

• 41720c2 #3862 Thanks @​yazaldefilimonepinto! - Forward className for custom components used with Field

• da58b29 #3858 Thanks @​alaanescobedo! - Remove use of deprecated StatelessComponent type in favor of FunctionComponent

• 5c01ee7 #3872 Thanks @​rajpatelbot! - FIX: Fixed resetForm function dependency issue

formik@2.4.3

Patch Changes

• 9e0a661 #3843 Thanks @​bonimba! - Fix FormikHelper and FieldHelperProps types

Commits

• c798145 Version Packages (#3966)
• f57ca9b Fix #3948 - Changing state was also causing change of initial value (#3949)
• c6ceb65 Fix grammatical error in field.md (#3928)
• ba15818 Fix broken code example in FastField API docs + update CONTRIBUTING.md `maste...
• f22eb8e chore: update Evan's handle (#3965)
• 0f960aa Merge pull request #3879 from jaredpalmer/changeset-release/main
• 724e0da Version Packages
• d7db9cd Add missing dependency @​types/hoist-non-react-statics, closes #3837 (#3860)
• 5edbd85 chore: skip actions if source files have not changed (#3880)
• ce305f5 Merge pull request #3871 from SophanySC/fix/ISSUE-3846-setValue-docs
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Assignees

The following users could not be added as assignees: stackrox/infra, stackrox/ui-dep-updaters. Either they do not exist or they do not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

[rhacs-bot]

A single node development cluster (infra-pr-1663) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1663 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f