-
- Downloads
Controlled upgrades (#47877)
* Initial commit of controlled upgrades
- new setting upgrade-threshold (`MB_UPGRADE_THRESHOLD`)
number 0-100
- conditionally removing latest from upgrade checks
AS OF RIGHT NOW IT ALWAYS REMOVES the latest.
Should help FE make this optional
* dumb mistake
* handle no latest version info
* implement and basic test
* More tests, refactor name
* more tests
* cljfmt does not like commas in source code.
* Just move site-uuid to the declaration and don't declare it
nothing is sacred in the settings order. no reason. i think i was just
trying to minimize the diff, which a dumb and ignoble goal.
* add context strings
* update unit tests
* use display version
* Have upgrade threshold include current major version
hopefully helps rotate people from early to late, and late to early
across major versions. Idea from sanya and quite nice!
---------
Co-authored-by:
Ryan Laurie <iethree@gmail.com>
Showing
- frontend/src/metabase/admin/settings/components/SettingsUpdatesForm/SettingsUpdatesForm.jsx 1 addition, 1 deletion...gs/components/SettingsUpdatesForm/SettingsUpdatesForm.jsx
- frontend/src/metabase/admin/settings/components/SettingsUpdatesForm/SettingsUpdatesForm.unit.spec.js 5 additions, 3 deletions...ents/SettingsUpdatesForm/SettingsUpdatesForm.unit.spec.js
- frontend/src/metabase/admin/settings/components/SettingsUpdatesForm/VersionUpdateNotice/VersionUpdateNotice.tsx 21 additions, 26 deletions...gsUpdatesForm/VersionUpdateNotice/VersionUpdateNotice.tsx
- src/metabase/config.clj 8 additions, 2 deletionssrc/metabase/config.clj
- src/metabase/public_settings.clj 51 additions, 9 deletionssrc/metabase/public_settings.clj
- test/metabase/public_settings_test.clj 67 additions, 0 deletionstest/metabase/public_settings_test.clj
Please register or sign in to comment