fix: use published extraction library 0.5.0 in the processor - #31
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Cloudflare verification failed because the processor's local file dependency could be installed without the library's compiled dist/index.js. Use the published all-things-youtube@0.5.0 release instead, pinned exactly in package.json and the registry lockfile with integrity verification.
The processor Docker build now uses its own directory, installs the published dependency, and verifies storyboard selection support. Remove local library compilation and install-links configuration. CI and Cloudflare use the same npm run verify entry point without a separate library-build prerequisite. Update deployment documentation to require publishing library changes before bumping the processor dependency.
Release and validation:
No Cloudflare build-setting change is required. Merge this PR to deploy the processor dependency change through the existing production workflow.