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

fix(docker): pin flowise version in Docker image to match release tag - #6670

Open
iruzen-dono wants to merge 1 commit into
FlowiseAI:mainfrom
iruzen-dono:fix/docker-version-pin
Open

fix(docker): pin flowise version in Docker image to match release tag#6670
iruzen-dono wants to merge 1 commit into
FlowiseAI:mainfrom
iruzen-dono:fix/docker-version-pin

Conversation

@iruzen-dono

Copy link
Copy Markdown

Description

The docker/Dockerfile used npm install -g flowise which installs whatever is latest on npm, causing version mismatch between the Docker image tag and the installed CLI version inside the container (e.g. image tagged 3.1.3 running CLI 3.1.2).

Changes

  • Added FLOWISE_VERSION build arg (defaulting to current release 3.1.3)
  • Changed to npm install -g flowise@${FLOWISE_VERSION}
  • Maintainers just need to update the default FLOWISE_VERSION on each release

Related Issue

Closes #6623

The docker/Dockerfile used 'npm install -g flowise' which installs
whatever is latest on npm, causing version mismatch between the Docker
image tag and the installed CLI version (e.g. image tagged 3.1.3
containing CLI 3.1.2).

This adds a FLOWISE_VERSION build arg (defaulting to current release)
so the installed version always matches the release tag.

Fixes FlowiseAI#6623
Copilot AI review requested due to automatic review settings July 26, 2026 10:53
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

Copilot AI 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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@iruzen-dono

Copy link
Copy Markdown
Author

Hi maintainers 👋 following up on this PR that pins the Flowise version in the Docker image to match the release tag — prevents drift between the released tag and the image users pull. Would appreciate a review when possible 🙏

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