Has the definition of "critical upgrade" changed?

dev
1

My Dashboard retrieves /admin/dashboard.json to get info about what version is running.

I’m fairly certain that until recently if any new beta release was available then critical_upgrade was set to true. It seems now that one some upgrades are considered “critical”. Is that true?

I really want to test for 2 cases. One in which a command-line rebuild is required and another if a new beta is available.

It looks like now to see if a new beta release is availble I need to compare installed_version and latest_version, but I’m looking at one site where latest_version is 3.3.0.beta2, but 3.3.0.beta3-dev is running here.

So I think I don’t have any idea what any of these mean. Maybe I want to check if missing_versions_count is 0?

 "version_check"=>
  {"installed_version"=>"3.3.0.beta3-dev",
   "installed_sha"=>"2a28cda15c4aef23850e780a63f60c47964839de",
   "installed_describe"=>"v3.3.0.beta2 +159",
   "git_branch"=>"tests-passed",
   "updated_at"=>"2024-05-27T20:04:21.625Z",
   "latest_version"=>"3.3.0.beta2",
   "critical_updates"=>false,
   "missing_versions_count"=>0,
   "version_check_pending"=>true,
   "stale_data"=>true},
 "has_unseen_features"=>true}

So here I see that the latest version is < the current version.

I’m think I’m sticking with these meanings:

  • if mission_versions_count > 0 then an upgrade is available
  • if critical_updates is true then I should strongly encourage people to do an upgrade (via my dashboard, which does a command line rebuild).
1 Like