#mastermind

Fixed a casing issue with git + go vendoring of the semver library dependency.

#tarball

Replace zip archive with tarball for ease of Docker container injection.

#context

In debug mode, cicada now indicates which app and version string trigger semver parsing errors. This provides more context to users when editing component patterns in the cicada configuration.

#dockerfiles

• Fix more gaps in querying component versions
• Add basic support for looking up explicit FROM base image OS versions in any Dockerfiles / *.[Dd]ockerfile files in the current directory tree
• Fix example ffmpeg version query
• Tune debian version query to work in environments without access to the lsb_release tool, which is often missing, for example, on compact, Debian Docker images

go1.21

• Update Go

#risky-business

Update to Go 1.20 for freebsd/riscv64 support.

#loongson

Upgrade Go to 1.19 for loong64 support in prebuilt binaries.

#splat

cicada now adheres more strictly to the explicitness of version strings in support timelines, when deciding whether the live component version matches the support timeline version.

Explicit zero values no longer behave as wildcards. This improves the accuracy of cicada findings.

#customization

The new configuration model has gained some basic documentation with Markdown prose and YAML commentary.

cicada now allows users to tune the early warning lead time, in month increments. Be advised to select a modest value:

Not too short that developers fail to migrate,
not too long that developers forget to migrate.

#respect

cicada now follows more conventional configuration directory structure:

• <current working directory>/cicada.yaml: main configuration file
• <current working directory>/.cicada: product cache

For example, a cicada.yaml file may be written in the top level directory of your software project.