v401 : New build available tag

[HansR]

The NewBuildAvailable webtag does give 0 while CMX itself raises the alarm that 4.1.0 is available, which it is (I won't uses that until it's problems are solved but that is not the issue here).

The URL http://192.168.178.143:8998/api/tags/pr ... dAvailable gives the page below:

Schermafbeelding 2024-06-17 065343.png

[Dador]

I confirm, it's the same for me.

But tag <#UpgradeAlarm> work fine.

[mcrossley]

Hans, what is the output of this? /api/tags/process.json?build&NewBuildNumber&NewBuildAvailable

[water01]

I got this Mark

{
"build": "4024",
"NewBuildNumber": "4024",
"NewBuildAvailable": "0"
}

[mcrossley]

Thanks, so that is OK. I need the output from someone running 4.0.0

[freddie]

From 4.0.1:

Code: Select all

{
  "build": "4023",
  "NewBuildNumber": "n/a",
  "NewBuildAvailable": "0"
}

[mcrossley]

OK, this is already fixed in 4.1.0

[HansR]

OK, this is already fixed in 4.1.0

OK, thnx.

[BeaumarisWX]

Hi Mark,
Build Tags still don't seem correct ?
Using "api/tags/process.json?version&build&NewBuildAvailable&NewBuildNumber"

"version":"4.1.3","build":"4028",""NewBuildAvailable":"0","NewBuildNumber":"0000"

Kind Regards,

[freddie]

I think that the tags are saying that you are on the latest version so there is no new build number available.

[BeaumarisWX]

Hi Freddie,
Thank you for the reply.
Yes well that makes sense, I was just used to the old returns.
Now I can rescript my status / checks page on my website to display the change correctly.
Kindest Regards,