Update Operator UI from v0.8.0-ffd9ff4 to v0.8.0-782ef0a

[github-actions]

@smartcontractkit/operator-ui

0.8.0-782ef0a

Minor Changes

• 53c5f87: rename fromAddress to fromAddresses in blockhashStoreSpec

• b286a55: Remove the maxGasPriceGWei field from VRF job details page.

• 3c7a06f: Add ability to show TOML config

  On the configuration screen, the user is now able to view their node's TOML config

• db6e6b4: Replaced "ETH balance" with "Native token balance"

• 935a76a: Display the Feeds Manager navigation in the mobile navigation drawer

Patch Changes

• 2ab39ec: Show node type
• f537fba: Fixes task run status display for unfinished tasks
• ffd9ff4: Display the name of job proposals in Feeds Manager
• 44bb788: Remove legacy config chain & node mutations.
• 69b88a0: Fixes infinite loop issue on Sign Out
• 059b169: Fix bug preventing selection of "Rows per page" in jobs/ID/runs page
• c91c2a5: Allow job deletion requests to be sent from FMS
• ba8eb05: dynamic config for legacy vs. TOML; syntax highlighting; expansion panels

0.7.0

Minor Changes

• d5517c9: Swap out compiler for testing and building for swc

  Using swc leads to significant performance gains in both CI and CD, with a 60% reduction in webpack build times, and a 25% reduction in test times.

  • Update to latest tsc version
  • Use swc for jest tests instead of ts-jest
  • Use swc for webpack builds
  • Update jest dependencies
  • Update jest snapshots based on JSON parsing changes in jsdom upgrade
  • Update gitignore to exclude yarn error logs
  • Fix serve config
  • Remove unused autobind decorator

• c6c81c1: Add "Key Admin Override" modal

  The /keys page in Operator UI now exposes several admin commands, namely:

  • An "abandon" checkbox to abandon all current transactions
  • Enable/disable a key for a given chain
  • Manually set the nonce for a key.

  See this PR for a screenshot example.

• 1ab4990: Fetch chainlink node build info during runtime

  Previously, the chainlink version and commit sha were baked into the static assets. Now, they're fetched during runtime via the /v2/build_info endpoint after the user has logged in. This enables the operator ui build phase to be isolated from the chainlink build phase, as we no longer need to know the version and commit sha of the chainlink node ahead of time.

[github-actions]

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

[cl-sonarqube-production]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information