Add version information to rendered output, alongside GitHub build context

[QuintinWillison]

@SimonWoolf observes in #105 (review), relating to version number living in package.json, that:

It effectively annexes package.json to be part of the spec -- you're implementing an sdk and need to know what string to set x-ably-version to implement the spec, but to find that info you need to look in package.json.

Which also means it's no longer sufficient to look at https://sdk.ably.com/builds/ably/specification/main/features/ , because package.json isn't exposed there, you need to go to the git repo to get that info. That seems a bit messier to me.

In response to that observation I am creating this issue, which will hopefully explain better my vision for how that sort of information will be laid out clearly going forwards.

The plan is to display the version number on every HTML page rendered in the micro-site generated by the assemble workflow in this repository, alongside other salient GitHub build context (already done).

See also:

• Existing footer implementation: Add GitHub build context to rendered output #12
• Related:
  • Workflow to build for tagged versions #96
  • Add Git tags for significant features spec evolution points #94

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-2859