Skip to content

chore: cleanup for Weblate 2026.8#4641

Open
nijel wants to merge 1 commit into
WeblateOrg:mainfrom
nijel:weblate-2026.8
Open

chore: cleanup for Weblate 2026.8#4641
nijel wants to merge 1 commit into
WeblateOrg:mainfrom
nijel:weblate-2026.8

Conversation

@nijel

@nijel nijel commented Jul 16, 2026

Copy link
Copy Markdown
Member

Remove compatibility that allowed both 2026.7 and 2026.8.

Remove compatibility that allowed both 2026.7 and 2026.8.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9b22c9a470

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread start
else
run_weblate collectstatic --noinput
fi
run_weblate collectstatic --noinput

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep 2026.7 static compression until the version bump

In this commit's tree the Dockerfile still pins WEBLATE_VERSION=2026.7.1, which is the pre-2026.8 code path that still needs weblate compress after collectstatic --clear. With this unconditional 2026.8 path, a normal runserver container built from this commit never generates the django-compressor offline output for 2026.7, so pages using compressed assets can fail or serve stale/missing CSS/JS until the Weblate version is actually bumped. Please keep the old probe/path or include the 2026.8 version bump in the same change.

Useful? React with 👍 / 👎.

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