BUG: content-build updates are not being added to CMS composer

[timcosgrove]

User Story or Problem Statement

We need content-build package updates to be added to CMS on an ongoing basis, so that CMS remains in sync with content-build's changes.

Description or Additional Context

At the time of this writing, the last content-build update merged to CMS was on January 9th, for version 0.0.3660: #20266

content-build is at version 0.0.3666 at time of writing: https://github.com/department-of-veterans-affairs/content-build/tree/v0.0.3666

Acceptance Criteria

• content-build updates are being correctly added to CMS composer

[timcosgrove]

Dependabot checks do find that a new content-build version is available: https://github.com/department-of-veterans-affairs/va.gov-cms/actions/runs/13123069888/job/36613360496#step:3:1026

But, by the end of the job, claim that no update is possible: https://github.com/department-of-veterans-affairs/va.gov-cms/actions/runs/13123069888/job/36613360496#step:3:1185

Still investigating.

[timcosgrove]

Running composer outdated will show updates for va-gov/content-build:

va-gov/content-build                           0.0.3666     0.0.3674     Front-end for VA.gov. This repository contains the code that

Noting that composer has this update marked as a major update rather than minor; this might be at the heart of why dependabot is currently refusing to update it.

[gracekretschmer-metrostar]

@timcosgrove is this work done or do you want us to move this work into the next sprint?

[edmund-dunn]

There is a bug in dependabot that is causing this issue. In the meantime, we will need to set up manual, twice-weekly updates of the va-gov/content-build dependency.