diegosouzapw 3a5b02b66a fix(security): require package-lock.json in Docker builds (Sonar S6476) ...

The previous Dockerfile fell back to \`npm install\` when no
package-lock.json existed, which lets the dependency tree float
between builds. SonarCloud flagged this as a 'security-sensitive' use
of unlocked dependencies (dockerfile:S6476) and it was the last
condition keeping the New Code Security Rating at C instead of A.

Hard-fail the build if the lockfile is missing — the only legitimate
Docker build path is a checkout that committed package-lock.json, and
that's how every CI image is produced today.

Also picks up env-doc drift cleanup: \`.env.example\` and
\`docs/reference/ENVIRONMENT.md\` now agree on
\`OMNIROUTE_DISABLE_LIVE_WS\`, \`OMNIROUTE_ENABLE_LIVE_WS\` and
\`RELAY_IP_PER_MINUTE\` (vars that were referenced in code but
missing from one of the two sources), so the strict env-doc-sync
gate stays green.

2026-05-26 10:37:49 -03:00

..

API_REFERENCE.md

Release v3.8.2 (#2503)

2026-05-23 01:46:59 -03:00

CLI-TOOLS.md

Release v3.8.2 (#2503)

2026-05-23 01:46:59 -03:00

ENVIRONMENT.md

fix(security): require package-lock.json in Docker builds (Sonar S6476)

2026-05-26 10:37:49 -03:00

FREE_TIERS.md

Release v3.8.2 (#2503)

2026-05-23 01:46:59 -03:00

meta.json

Release v3.8.3 (#2617)

2026-05-24 18:05:58 -03:00

openapi.yaml

fix(ci): green up release/v3.8.4 pipeline (lint, unit, build paths)

2026-05-26 06:13:26 -03:00

PROVIDER_REFERENCE.md

Release v3.8.2 (#2503)

2026-05-23 01:46:59 -03:00