Hwaro::Core::Build::CacheMetadata

Output files the last build produced that no cache ENTRY covers: the taxonomy index/term pages, their pagination pages and their feeds. Those have no content file, so nothing else remembers them, and a --cache build (which keeps the output directory) left the term page of a tag whose last post was deleted published forever. Stored relative to the output directory so moving the workspace, or switching between an absolute and a relative -o, does not strand them. Empty for caches written before this field existed: the first build after an upgrade records the set and prunes from the next one.

Output files the last build produced that no cache ENTRY covers: the taxonomy index/term pages, their pagination pages and their feeds. Those have no content file, so nothing else remembers them, and a --cache build (which keeps the output directory) left the term page of a tag whose last post was deleted published forever. Stored relative to the output directory so moving the workspace, or switching between an absolute and a relative -o, does not strand them. Empty for caches written before this field existed: the first build after an upgrade records the set and prunes from the next one.

hwaro version that wrote this cache. Every hash above fingerprints the inputs (sources, templates, config, cascade) — none of them move when only the renderer changes, so a build that fixes how markdown becomes HTML would otherwise never reach a --cache site: its pages are unedited, so they stay skipped indefinitely. Treating a version change as a full invalidation costs one cold build per upgrade and makes every future rendering fix actually land.

Written by Cache#save (which always stamps the running version, so the in-memory rebuilds in set_global_checksums/set_set_fingerprints cannot drop it) and compared by Cache#load. Default "" so caches written before this field existed invalidate once on upgrade.

hwaro version that wrote this cache. Every hash above fingerprints the inputs (sources, templates, config, cascade) — none of them move when only the renderer changes, so a build that fixes how markdown becomes HTML would otherwise never reach a --cache site: its pages are unedited, so they stay skipped indefinitely. Treating a version change as a full invalidation costs one cold build per upgrade and makes every future rendering fix actually land.

Written by Cache#save (which always stamps the running version, so the in-memory rebuilds in set_global_checksums/set_set_fingerprints cannot drop it) and compared by Cache#load. Default "" so caches written before this field existed invalidate once on upgrade.

Output directory this cache was built for, RELATIVE to the project root when it lives inside it. Alternating -o dist and -o preview from one checkout must invalidate (each tree holds pre-edit files the source hashes would otherwise mark up to date), but merely moving the workspace must NOT — hence relative, not absolute.

Output directory this cache was built for, RELATIVE to the project root when it lives inside it. Alternating -o dist and -o preview from one checkout must invalidate (each tree holds pre-edit files the source hashes would otherwise mark up to date), but merely moving the workspace must NOT — hence relative, not absolute.

Fingerprints of the global page/section sets. Listing pages (homepage, section indexes, archives, taxonomy widgets) render content derived from these sets even when their own source is unchanged, so a change here forces those pages to re-render on an incremental build. Default "" so older cache files (without these keys) load and rebuild once.

Fingerprints of the global page/section sets. Listing pages (homepage, section indexes, archives, taxonomy widgets) render content derived from these sets even when their own source is unchanged, so a change here forces those pages to re-render on an incremental build. Default "" so older cache files (without these keys) load and rebuild once.

Static and bundle copies made while their source mtime was still inside its timestamp tick (#859). The copy is stamped with the source mtime, so a same-size rewrite in that tick matches it exactly; the next build byte-compares these instead of trusting the match.

Static and bundle copies made while their source mtime was still inside its timestamp tick (#859). The copy is stamped with the source mtime, so a same-size rewrite in that tick matches it exactly; the next build byte-compares these instead of trusting the match.

Digest of what templates read OUTSIDE the tracked files: the build-derived globals (asset-bundle manifest, auto-include tags and their ?v=) plus the current value of every recorded render read (env() names, load_data() files, resize_image() sources — see TemplateEngine.record_render_read). Only the digest and the read KEYS are stored: an env value may be a secret. "" (a cache written before this existed) compares as unknown, not as a change.

Digest of what templates read OUTSIDE the tracked files: the build-derived globals (asset-bundle manifest, auto-include tags and their ?v=) plus the current value of every recorded render read (env() names, load_data() files, resize_image() sources — see TemplateEngine.record_render_read). Only the digest and the read KEYS are stored: an env value may be a secret. "" (a cache written before this existed) compares as unknown, not as a change.