Skip to content

fix(deploy): refresh frontend dependencies on every release#61

Merged
xiaou61 merged 1 commit into
masterfrom
hotfix/v2.4.1-dependency-refresh
Jul 15, 2026
Merged

fix(deploy): refresh frontend dependencies on every release#61
xiaou61 merged 1 commit into
masterfrom
hotfix/v2.4.1-dependency-refresh

Conversation

@xiaou61

@xiaou61 xiaou61 commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • always run deterministic npm ci for both frontends during production releases
  • remove the stale-node_modules shortcut that skipped newly added local packages
  • add a shell regression contract and include both deployment scripts in syntax checks

Root Cause

The self-hosted production runner intentionally preserves frontend node_modules. The deployment script only installed dependencies when that directory was absent, so v2.4.1 did not install the new file:../code-nest-design-system package.

Verification

  • bash -n scripts/ci-server-build-deploy.sh scripts/ci-server-build-deploy.test.sh scripts/deploy-release.sh
  • bash scripts/ci-server-build-deploy.test.sh
  • ./scripts/code-nest-eval.ps1 -Tier hygiene
  • production runner admin and user builds passed as the actions-runner user
  • v2.4.1 production deployment attempt 3 completed successfully

The production runner retained stale node_modules and skipped installing the new shared design-system package. Always run npm ci for both frontends and enforce the behavior with a shell regression contract.
@xiaou61
xiaou61 merged commit e189107 into master Jul 15, 2026
7 checks passed
@xiaou61
xiaou61 deleted the hotfix/v2.4.1-dependency-refresh branch July 15, 2026 02:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant