Skip to content
This repository was archived by the owner on Aug 13, 2026. It is now read-only.

fix: pin Docker image package version - #6642

Open
zcxGGmu wants to merge 1 commit into
FlowiseAI:mainfrom
zcxGGmu:codex/issue-6623-pin-docker-version
Open

fix: pin Docker image package version#6642
zcxGGmu wants to merge 1 commit into
FlowiseAI:mainfrom
zcxGGmu:codex/issue-6623-pin-docker-version

Conversation

@zcxGGmu

@zcxGGmu zcxGGmu commented Jul 18, 2026

Copy link
Copy Markdown

Summary

  • install the Flowise npm package version requested by the Docker Hub image tag instead of unpinned latest
  • keep latest as the Dockerfile default for existing manual builds
  • verify versioned images report a CLI version matching their published tag

Fixes #6623

Testing

  • python -X utf8 -c "import yaml; ..." (workflow YAML parse)
  • npx --yes prettier@2.7.1 --check .github/workflows/docker-image-dockerhub.yml
  • git diff --cached --check
  • npm view flowise@3.1.2 version
  • npm view flowise@v3.1.3 version

The local Docker Desktop Linux engine did not become responsive, so I could not complete a local image build. The workflow now performs the end-to-end CLI version assertion after publishing the manifest.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the Dockerfile to support installing a specific version of Flowise during the build process. It introduces a new build argument FLOWISE_VERSION (defaulting to latest) and updates the global npm installation command to use this argument. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

dblagbro added a commit to dblagbro/flow-wiser that referenced this pull request Aug 12, 2026
…ill merging (#18)

The 2026-08-05 snapshot was taken because "upstream repository moves to public
archive on 2026-08-10, which locks issues and pull requests". That did not
happen. Verified 2026-08-12: archived=false, disabled=false, comments still
working, and three pull requests merged on 2026-08-07 -- after the documented
2026-07-29 code freeze and after the snapshot was taken.

Upstream is frozen, not closed. Contributions can still be commented on and, on
this evidence, still merged.

This contradicts docs/PROJECT-LOG.md, docs/product.md and docs/STATUS.md, which
all assert the archive happened. It also makes a public comment on upstream
FlowiseAI#6706 wrong. Both are flagged in DELTA-2026-08-12.md rather than corrected here,
because the licensing narrative is REVIEW REQUIRED and belongs to a human.

Synced:
  * 3 new PRs captured as git am-able patches -- FlowiseAI#6714, FlowiseAI#6723, FlowiseAI#6725
  * 3 upstream-MERGED fixes this fork does not have, captured to
    merged-after-snapshot/ -- FlowiseAI#6680, FlowiseAI#6708, FlowiseAI#6709, all maintainer-authored
  * prs/index.json refreshed 347 -> 346, issues 698 -> 701
  * both indexes normalised to a single JSON array; the originals were 11
    concatenated per-page arrays that parse only with jq -s. Data was complete
    in both, only the shape changed.

Licence check applied to all six new patches: no diff hunks against
packages/server/src/enterprise/ or IdentityManager.ts. All clean, no stripping
required, and no hunk content was read to determine it -- decisions made on the
diff --git path headers alone, per docs/CLEANROOM-PROTOCOL.md.

DELTA-2026-08-12.md also records where Flow-Wiser has already solved a still-open
upstream PR, with the fork's fix being the more complete one in every confirmed
case: FlowiseAI#6670 and FlowiseAI#6642 (the unpinned Docker version -- this fork's founding
defect, still open upstream from two independent reporters), FlowiseAI#6706
(connect-sqlite3), and FlowiseAI#4805 (Node 22, open since 2025-07-06 for the change
ADR-0004 completed this week across ten locations rather than three).

Contributing any of it back is an outward action and is left for authorization.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docker image flowiseai/flowise:3.1.3 contains Flowise CLI version 3.1.2

2 participants