Frontend release versions

GithubReleaseDownload("latest-testing", ...) selects the highest published numeric v...-TESTING tag during deployment, after its GitHub authentication files have been installed. version remains the configured selector; resolved_version exposes the selected tag after the download update. Fixed pins are returned unchanged and do not require a release lookup.

For multiple archives, pass release=first_download to subsequent GithubReleaseDownload instances with the same package and selector. Add the first download before the others so that all archives use one selected release.

Ordinary batou File templates render during configuration, before aliases have been resolved. Use GithubReleaseContent after the download and extraction to render release-dependent configuration during deployment:

from risclog.batou.github import (
    GithubReleaseContent,
    GithubReleaseDownload,
)

self.frontend_release = GithubReleaseDownload(
    self.frontend_version,
    package="risclog.frontend",
    file="claimx.zip",
)
self += self.frontend_release
# Add archive extraction here, before rendering its configuration.
self += GithubReleaseContent(
    "frontend/config.js",
    release=self.frontend_release,
    source="config.js",
    template_context=self,
)

In config.js, use {{args.release.resolved_version}} for appVersion. The usual component template context and other template_args remain available. Like batou Content, this helper manages file contents only; the target directory must already exist. An unresolved alias fails explicitly during deployment rather than writing latest-testing. Prediction reports a pending change without looking up an unresolved alias or writing the config.

Tests

Run tests:

$ ./pytest