Use semantic versioning for released versions of the service

[elrayle]

Description

The production service has been using incremental numbers for versions. This issue proposes switching to use Semantic Versioning. This approach to versioning makes it easier for downstream users to gauge the level of change from the version number.

As part of this work, releases will be documented using GitHub releases. This provides information about what changed and what actions are required to update to the new release.

Related Work

Related Work

• https://github.com/clearlydefined/website/issues/1034
• https://github.com/clearlydefined/crawler/issues/540
• https://github.com/clearlydefined/website/issues/1033
• https://github.com/clearlydefined/service/issues/1026
• https://github.com/clearlydefined/crawler/issues/539

[elrayle]

Thoughts on process...

• update to semver versioning
  • update package.json to set version to v1.0.0 in master
  • add release based on current prod branch
  • deploy prod using Azure devops
• update prod to latest dev
  • determine if current service code is ready for prod release
  • update version based on semver
  • create release for new version
  • deploy prod using Azure devops

[elrayle]

Release v1.0.0 was published on Feb 1, 2024. This completes the work for this issue.