w3c/wot-scripting-api

Use a different tag for unstable npm packages

relu91 opened this issue · 3 comments

relu91 commented

From TD Call of 02.08:

  • Luca: This is wrong semver. If we use date, it would be better to use ISO date format. For future versions, we can use _pre20231223 to be more aligned with common practices.

Originally posted by @egekorkan in w3c/wot-thing-description#1863 (comment)

As @lu-zero mentioned is better to use the ISO date format because it maintains the lexical graphical order (this makes npm install work also with pre-releases). After the 1.1.0 publication, we can switch to this new approach.

relu91 commented

See also #224

relu91 commented

Call 22/01:

  • @danielpeintner we are following TD json-schema version for TD and TM. We have to discuss this point together with TD group.
  • Scripting API tags is different and unrelated (we are now at 0.8.x).
  • @relu91 we need to be consistent between TD types and Scripting API versioning (using the same tag format).
danielpeintner commented

At the moment there does not seem to be a corresponding issue, it is rather a PR for now (see w3c/wot-thing-description#1969).

WAITING FOR ISSUE TO BE CREATED/LINKED