GitHub user artur282 closed the discussion with a comment: When would a new
docker image be released containing the changed of PR 43073?
No released image contains it yet, but you don't need a custom build: the merge
commit of PR 43073 already has a published, pinned image tag, and the change
will land in 6.2.0.
**Where the fix stands**
```
$ gh api repos/apache/superset/pulls/43073 -q
'{title,merged_at,merge_commit_sha,base}'
{"title":"fix(cache): warm native dashboard filter
defaults","merged_at":"2026-08-13T05:30:49Z",
"merge_commit_sha":"685f26b1bf9805523005da6d92913e500bccf905","base":"master"}
```
The newest release tag is `6.1.0` (published 2026-05-13), i.e. ~3 months
*before* that merge, so no 6.1.0/6.0.x image carries this code.
**Images are published per commit, not only per release**
`.github/workflows/docker.yml` triggers on `push` to `master` and
`[0-9].[0-9]*` (lines 3-10) and pushes `apache/superset` images; the
release-time tag behaviour is documented in `RELEASING/README.md`, section "###
Docker Releases" (~line 511): *"Docker release with proper tags should happen
automatically as version tags get pushed"*.
The image built from the merge commit is on Docker Hub right now:
```
$ curl -s
https://hub.docker.com/v2/repositories/apache/superset/tags/685f26b1bf9805523005da6d92913e500bccf905
{"name": "685f26b1bf9805523005da6d92913e500bccf905",
"last_updated": "2026-08-13T05:50:00Z",
"digest":
"sha256:06c2bb2f5ab649a6228fca26d74128efeb123d07b0f10855df06ff96c6df287d"}
```
The 7-char alias `apache/superset:685f26b` exists too, pushed
2026-08-13T05:50:02Z — roughly 20 minutes after the merge.
**Do not rely on `latest` for this.** Per the same RELEASING section, `latest`
is force-assigned to the most recent *release*, and
`.github/workflows/scheduled-docker-image-refresh.yml` (cron `0 6 * * 1`) only
re-layers the most recent release tag + `latest` on a refreshed base image.
Both `apache/superset:6.1.0` and `apache/superset:latest` currently report
`last_updated 2026-09-07T06:13`, i.e. the same 6.1.0 code with newer base
layers.
**Actionable workaround, no build from source**
`docker-compose-image-tag.yml:27` is
```yaml
x-superset-image: &superset-image
apachesuperset.docker.scarf.sh/apache/superset:${TAG:-latest-dev}
```
so a published image can be pinned by overriding `TAG`:
```bash
export TAG=685f26b # merge commit of PR 43073, published by CI
docker compose -f docker-compose-image-tag.yml up -d
```
That is the exact artifact CI builds for master (also `docker pull
apache/superset:685f26b`) — a supported image, just not a released version.
**Timeline for an official release**
The next version is 6.2.0: master's `superset-frontend/package.json` is
`0.0.0-dev`, and a `6.2` branch already exists carrying cherry-picks (tip
`fd55308`, 2026-07-23). The fix is on master (`compare/685f26b...master`
reports "ahead"). If you need it in a patch release on the 6.1 line instead, it
would have to be backported to the `6.1` branch (tip `c37118e`, 2026-07-17);
nothing has been backported as of today.
One doc nit for the maintainers while this thread is open:
`RELEASING/README.md` (~line 520) says `docker.yml` implements a
`workflow_dispatch` trigger, but that workflow currently only has
`push`/`pull_request` triggers; the manual re-publish path with `release` /
`git-ref` / `force-latest` inputs lives in
`.github/workflows/tag-release.yml:8-23`.
GitHub link:
https://github.com/apache/superset/discussions/43823#discussioncomment-18406205
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
