Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a different tag for unstable npm packages #488

Open
relu91 opened this issue Aug 9, 2023 · 3 comments
Open

Use a different tag for unstable npm packages #488

relu91 opened this issue Aug 9, 2023 · 3 comments

Comments

@relu91
Copy link
Member

relu91 commented Aug 9, 2023

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
Copy link
Member Author

relu91 commented Jan 22, 2024

See also #224

@relu91
Copy link
Member Author

relu91 commented Jan 22, 2024

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
Copy link
Contributor

danielpeintner commented Feb 20, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants