Bump CAPI model to include new video captions field - #96
Open
RikRootsGuardian wants to merge 2 commits into
Open
Bump CAPI model to include new video captions field#96RikRootsGuardian wants to merge 2 commits into
RikRootsGuardian wants to merge 2 commits into
Conversation
RikRootsGuardian
marked this pull request as draft
April 15, 2026 13:20
gu-scala-library-release Bot
added a commit
that referenced
this pull request
Apr 15, 2026
….2026-04-15T1324.35a965c1 published by RikRootsGuardian RikRootsGuardian published release version 2.0.0-PREVIEW.rjr-bump-capi-model-to-include-new-video-caption-field.2026-04-15T1324.35a965c1 using gha-scala-library-release-workflow: https://github.com/guardian/gha-scala-library-release-workflow Release-Version: 2.0.0-PREVIEW.rjr-bump-capi-model-to-include-new-video-caption-field.2026-04-15T1324.35a965c1 Release-Initiated-By: https://github.com/RikRootsGuardian Release-Workflow-Run: https://github.com/guardian/content-api-firehose-client/actions/runs/24457071027 Release-Notes: #96
Contributor
|
@RikRootsGuardian has published a preview version of this PR with release workflow run #43, based on commit 35a965c: 2.0.0-PREVIEW.rjr-bump-capi-model-to-include-new-video-caption-field.2026-04-15T1324.35a965c1 Want to make another preview release?Click 'Run workflow' in the GitHub UI, specifying the rjr-bump-capi-model-to-include-new-video-caption-field branch, or use the GitHub CLI command: gh workflow run release.yml --ref rjr-bump-capi-model-to-include-new-video-caption-field Want to make a full release after this PR is merged?Click 'Run workflow' in the GitHub UI, leaving the branch as the default, or use the GitHub CLI command: gh workflow run release.yml |
This was referenced Apr 20, 2026
RikRootsGuardian
marked this pull request as ready for review
May 18, 2026 15:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Composer users need an easier way to update captions for video atoms. The current process of updating them in MAM is laborious and prevents us from showing different captions for the same video on different articles, which is sometimes helpful.
The work in this PR is part of a chain of PRs to add a new
captionfield to the atom editor in Composer. This field should:titlevalue, set in the Media Atom Maker toolSee the Rethink media atom captions in Composer issue (in the Arts&Pubs project) for further details
Testing
Testing plan document
Deployment
Some PRs include model pre-releases. Before deploying to PROD, these pre-releases will need to become full releases, and code in affected PRs updated to reflect these changes.
TODO: come up with an appropriate sequencing for merging and closing PRs. The PRs do not need to all be deployed at the same time, but some - such as those requiring associated releases - need to be performed before others.
TODO: complete the description for the purpose of this PR
Note: we need to do work here to try and fix a version clash in a similar PR in the

apple-newsrepo