Versioning of packages and countdown js/css assets

[gadenbuie]

We have a number of different versions to consider:

• The R package version
• The Quarto extension version
• The Python package version
• The countdown JS/CSS assets version in lib/
• The countdown JS/CSS assets in each package

It would be helpful to have a method for versioning each of these items. My proposal:

1. Package and extension code is versioned independently of the core countdown assets
   • These version should agree in the minor element, e.g. 0.2.x of any package/extension code should implement the same behaviors.
   • Patch versions increment with local changes to the package/extension code
2. The core countdown assets maintain their own version number that is used by the html dependency.

We can add a header to lib/countdown.js that tracks its version number, which can be read by the package code or used in the update process when updating the extension.

[coatless]

I think the plan surrounding independent versioning is spot-on. Though, we may want to add one more decimal point. (If only R supported semantic versioning with x.y.z-a.1; but alas we're stuck with x.y.z.a.1).

Could we offload writing versions into a config.R/config.py file? That would make it easier to track the embedded version without introducing a diff that might detract from library changes.

e.g.

/* countdown: 0.1.1 */

.countdown {
  /* CSS */
}

echo "countdown_embedded <- '${COUNTDOWN_ASSET_VERSION}'" >> config.R

This would generate:
config.R

countdown_embedded <- '0.1.1'