Coverage chart / polkadot{.js}
Keep polkadot{.js} up to date on your Mac
polkadot{.js} is covered by Floodtide. It shows up in your update list the moment a newer version ships, and updates in one click along with everything else on this Mac.
How polkadot{.js} gets updated
Floodtide reads the Homebrew catalog, a community-maintained index of Mac software, to learn which version of polkadot{.js} is current. When yours is behind, the row appears under Updates with the version it will move to and the download size. Pressing Update, or Update All, does the rest:
- The vendor’s own build is downloaded, several apps at a time, with real progress.
- The download is verified against the checksum the catalogue publishes.
- polkadot{.js} is asked to quit politely if it is open, and never forced.
- The bundle is swapped and the old version kept for seven days, so Undo Last Update always works.
- The replacement’s code signature is checked; a build signed worse than the one you had is rolled back automatically.
If polkadot{.js} lives in a folder macOS protects, the swap asks for your administrator password once for the whole batch, exactly as the Finder does when you install anything by hand.
Questions about polkadot{.js}
Does Floodtide update polkadot{.js}?
Yes. polkadot{.js} is in the Homebrew catalog that Floodtide reads, so it appears in your update list automatically when a newer version is published, with no configuration.
How does Floodtide install a new version of polkadot{.js}?
It downloads the vendor's official build, verifies it against the checksum the catalogue publishes, quits polkadot{.js} if it is running, swaps the bundle, and keeps the previous version for seven days so the update can be undone.
Will updating polkadot{.js} lose my settings?
No. Floodtide replaces the application bundle only. Preferences, licences and documents live outside it and are untouched.