Skip to content

2.85.2a2

2.85.2a2: Fix CI build by aligning with main's lockfile
@Kelsey-Ethyca Kelsey-Ethyca tagged this 18 May 18:12 
The regenerated lockfile pulled minor-bumped versions that broke the
production build:
- next 16.2.3 -> 16.2.6 tightened CSS modules pure-selector enforcement
- antd 6.3.2 -> 6.4.3 tightened Form.setFieldsValue typings

Main's CI doesn't surface these because the docker build's turbo cache
skips the actual frontend compilation step. Our regenerated lockfile
busted the cache and exposed the latent issues.

Fixes:
- Restore lockfile to match main's pins exactly (only adds entries for
  demo/april deps; doesn't bump anything main already had)
- Scope the diffStatus :global selectors in AccessPolicyEditor.module.scss
  under .canvasContainer so they pass CSS modules pure-selector check.
  (Standalone :global(...) rules are impure — this is a latent issue on
  main that's masked by turbo cache.)
- Add @ant-design/x-markdown to transpilePackages in next.config.js
  because its /es entry uses a directory import that Node ESM rejects
  during page data collection. (Also latent on main.)
Assets 2
Loading