task: #3625827 Let CI enforce the committed yarn.lock

Rajab Natshahrequested to merge
issue/ace_editor-3625827:3625827-enforce-lock into 2.0.x

Issue: https://www.drupal.org/i/3625827

Changes

yarn.lock is now committed, but CI still carried the setup written for a project without one: a comment saying no lock was committed, and YARN_ENABLE_IMMUTABLE_INSTALLS: "false" so yarn could create it. That override let each run rewrite the lock instead of installing exactly what it pins.

Drops both, so CI uses yarn 4's default immutable install and fails if package.json and yarn.lock ever disagree.

Testing

yarn install --immutable passes locally against the committed lock. This pipeline is the check in CI.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports