You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nx's publishing of information to their releases JSON API is not currently considered reliable enough for hands off automation.
Only the develop branch will use online version information from the CreateMatrix utility at build time.
The main branch still relies on the static Version.json file I manually curate and test, when observing version changes via VisualPing.
I will enable online updates for the main branch when I am confident in the CreateMatrix and releases.json logic.
Examples of problems:
Nx promoted v5 to stable, then removed v5 and reverted v4 back to stable, this breaks the stable tag logic as Nx does not support downgrades.
The contents of the releases.json file is not reliable. e.g. on occasion it would contain raw error messages instead of JSON:
This XML file does not appear to have any style information associated with it. The document tree is shown below. ...
Nx's publishing of information to their releases JSON API is not currently considered reliable enough for hands off automation.
Only the
develop
branch will use online version information from theCreateMatrix
utility at build time.The
main
branch still relies on the staticVersion.json
file I manually curate and test, when observing version changes via VisualPing.I will enable online updates for the
main
branch when I am confident in theCreateMatrix
andreleases.json
logic.Examples of problems:
v5
to stable, then removedv5
and revertedv4
back to stable, this breaks thestable
tag logic as Nx does not support downgrades.releases.json
file is not reliable. e.g. on occasion it would contain raw error messages instead of JSON:This XML file does not appear to have any style information associated with it. The document tree is shown below. ...
{"resultCode":500,"errorText":"Unexpected error somewhere inside"}
The text was updated successfully, but these errors were encountered: