Skip to content

fix(version): cache the upstream SHA instead of the verdict - #295

Open
fjen wants to merge 1 commit into
coda-oa:developfrom
fjen:fix/version-caching
Open

fix(version): cache the upstream SHA instead of the verdict#295
fjen wants to merge 1 commit into
coda-oa:developfrom
fjen:fix/version-caching

Conversation

@fjen

@fjen fjen commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator
  • Version check relied on implicit django cache, which is now set explicitly. We still default to locmemcache, should change that whenever we want to deploy more workers or get more use of the caching mechanisms.
  • Failed github api fetches are now handled properly and not cached as a proper result.
  • Update check can be disabled via .env.

fixes #293

Cache the fetched SHA per branch and recompute the verdict per call, so a
deploy inside the cache window is no longer answered with the previous
commit's result. Failures now expire under their own short TTL and degrade
to the last known-good SHA instead of refetching per request. Cache errors
are logged and treated as a miss. Declares CACHES in base.py, gates the
outbound call behind CODA_UPDATE_CHECK, and memoises the git/baked-file
primitives rather than the protocol methods
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant