Milvago 1.0.6

What's Changed

• Sign-in in Milvago's design, second-factor devices, masking and sign-in fixes by @lfmilvagoai in #30

Full Changelog: v1.0.5...v1.0.6

Milvago 1.0.5

What's Changed

• Bump the npm group in /console with 5 updates by @dependabot[bot] in #20
• Bump keycloak/keycloak from 26.7.4 to 26.8.0 by @dependabot[bot] in #17
• Bump axllent/mailpit from v1.31.2 to v1.31.3 by @dependabot[bot] in #16
• Bump the actions group with 2 updates by @dependabot[bot] in #22
• Update Vitest to 5.0.3 and pin patched source-map-js by @dependabot[bot] in #23
• Release server 1.0.5 by @lfmilvagoai in #29

New Contributors

• @dependabot[bot] made their first contribution in #20

Full Changelog: v1.0.4...v1.0.5

Milvago 1.0.4

What's Changed

• Prepare server 1.0.4 and stage dependency updates on dev by @lfmilvagoai in #21

Full Changelog: v1.0.3...v1.0.4

Milvago 1.0.3

What's Changed

• Release 1.0.3: restore early WSL and Docker CLI checks by @lfmilvagoai in #15

Full Changelog: v1.0.2...v1.0.3

Milvago 1.0.2

Milvago 1.0.2

The installer now defaults to local access when the public URL is left blank. Open http://localhost:4020 on the server; the gateway binds only to 127.0.0.1:4020. From another computer, use an SSH tunnel. Supplying a public URL preserves the existing reverse-proxy installation flow.

curl -fsSL https://get.milvago.ai | bash

To select local access without a prompt:

curl -fsSL https://get.milvago.ai | MILVAGO_PUBLIC_URL='' bash

With no controlling terminal and no URL, local mode is selected. Invalid nonempty URLs are rejected. An existing confirmed URL is preserved; conflicting input stops installation. No GitHub credentials are needed.

Validation includes URL selection tests, real Docker tests for public and localhost configurations, Keycloak OIDC discovery, server and console tests, image vulnerability scanning, cosign signing and verification, and anonymous production image pull.

The server image uses an exact version and digest recorded in release.json. Agent and extension remain at 0.6.4. Existing installations receive the new behavior when this installer is run.

Milvago 1.0.1

What's Changed

• Prepare 1.0.1: public installation and production hardening by @lfmilvagoai in #13

Full Changelog: v1.0.0...v1.0.1

Milvago 1.0.0

Milvago server 1.0.0

Public image: ghcr.io/milvago-ai/milvago-server:1.0.0

Digest: sha256:f49cf2bd8a46222c04954f0fd8107cdd5838169b46f6e3049a83b977a99df588

The image passed vulnerability scanning, cosign signing and verification, and anonymous Docker pull.

Install

No GitHub account, token, or registry login is required. Download the release assets and verify their checksums:

mkdir -p milvago-install && cd milvago-install
release_url=https://github.com/Milvago-AI/milvago-server/releases/download/v1.0.0
curl -fLO "$release_url/install-private.sh"
curl -fLO "$release_url/release.json"
curl -fLO "$release_url/SHA256SUMS"
sha256sum --check SHA256SUMS
bash install-private.sh

The filename install-private.sh is historical. All installation downloads are public. The script checks prerequisites, asks for the public Milvago URL on the terminal, and installs the pinned image with the verified Community agent 0.6.4 bundle. For unattended execution, set MILVAGO_PUBLIC_URL to the exact HTTP or HTTPS origin.

Piped execution is also supported:

curl -fsSL https://get.milvago.ai | bash

Installer correction — 2026-09-29

The installer assets were replaced to remove the obsolete GitHub token requirement and correct piped startup. URL input uses /dev/tty; startup handles the absence of a script file and ignores the current directory as an installation when piped. A final main invocation ensures the script body is parsed before installation starts.

The installed profile now starts Keycloak in production mode. Mailpit is disabled by default and restricted to an optional development profile with user 65532:65532 and all capabilities dropped. Rerunning the installer stops an existing Mailpit container without deleting its captured messages, removes only the factory SMTP settings, and preserves custom SMTP settings. Configure and test a real SMTP service before using invitations or password-reset email.

Use a dedicated sudo-capable installation account without adding it to the Docker group. Docker user namespace remapping remains disabled pending volume and networking qualification.

The server image and server source commit are unchanged. release.json records the separate installer source commit d127a0d19fdd78382b0717beb29021eb47c97f19; SHA256SUMS covers the corrected files. Download all three assets again if you obtained an earlier installer. Existing installations receive these changes only when the new installer is run.

Community agent and extension 0.6.4: https://github.com/Milvago-AI/milvago-agent/releases/tag/community-agent-v0.6.4

The Windows MSI does not yet carry an Authenticode publisher signature. Update manifests are signed with Ed25519.