chore(deps): core-styles v2.55 + section--accent

[wesleyboar]

Overview

Update to Core-Styles v2.55 for:

• accessibility fixes to .sections
• new .section style accent
• support Bootstrap v4 media object
• new script to create page to test sections

Related

• required by fix: a11y issues - color contrast Core-CMS-Custom#531

Changes

• updated Core-Styles
• added section--accent`

Testing

1. make build
2. make start
3. Create a page with:
   • two sections, one after the other
   • each section has <h2> and text
   • try different section combinations
4. Verify UI matches sections of:
   • fix: section heading color contrast Core-Styles#625
   • feat: restore border between watching sections Core-Styles#624

UI

[qodo-code-review]

Review Summary by Qodo

Update Core-Styles to v2.55.0 with accessibility improvements

✨ Enhancement

Walkthroughs

Description

• Update Core-Styles dependency to v2.55.0
• Includes accessibility fixes for sections
• Adds new section--accent style variant
• Enables Bootstrap v4 media object support

Diagram

flowchart LR
  A["package.json"] -- "update dependency" --> B["@tacc/core-styles v2.55.0"]
  B -- "provides" --> C["Accessibility fixes"]
  B -- "provides" --> D["section--accent style"]
  B -- "provides" --> E["Bootstrap v4 media support"]

Loading

File Changes

1. package.json Dependencies +1/-1

Bump Core-Styles dependency to v2.55.0

• Updated @tacc/core-styles from v2.54.1 to v2.55.0
• Brings in accessibility improvements and new styling options

package.json

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1)   📘 Rule violations (0)   📎 Requirement gaps (0)   🎨 UX Issues (0)

🐞\ ☼ Reliability (1)

1. Node version incompatibility 🐞 ☼

Description

After bumping @tacc/core-styles to 2.55.0, the dependency declares engines.node >=20.x, but
the Docker build stage runs node:18 and executes npm ci/npm run build, which runs Core-Styles
code under an unsupported Node version. This can cause npm ci EBADENGINE failures (if engines are
enforced) and/or runtime build failures when bin/build-css.js imports Core-Styles.

Code

package.json[24]

+    "@tacc/core-styles": "^2.55.0"

Evidence

The PR changes the Core-Styles version, and the resolved package metadata for
@tacc/core-styles@2.55.0 requires Node 20+, while the repository’s asset build runs in a Node 18
Docker stage and directly require()s Core-Styles during npm run build.

package-lock.json[1405-1417]
Dockerfile[39-51]
bin/build-css.js[3-31]
package.json[9-12]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`@tacc/core-styles@2.55.0` requires Node `>=20.x` but the repo builds CSS in Docker using `node:18` and the repo-level `package.json` advertises `node >=16`. This mismatch can break `npm ci` (engine enforcement) and/or the runtime execution of `bin/build-css.js` that imports Core-Styles.

### Issue Context
- Docker build stage installs deps via `npm ci` and runs `npm run build`.
- `npm run build` calls `bin/build-css.js`, which `require()`s `@tacc/core-styles`.
- Lockfile shows `@tacc/core-styles@2.55.0` requires Node 20+.

### Fix Focus Areas
- Update Node build image to Node 20+ (and keep npm compatible):
 - Dockerfile[39-51]
- Align the repo’s declared engines with what is actually required (or revert/pin core-styles to a Node-18-compatible version if you must stay on Node 18):
 - package.json[9-12]
 - package.json[23-25]
- Validate the lockfile still resolves correctly after the Node/version decision:
 - package-lock.json[1405-1417]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more