Enhance npm tarball propagation handling in CI/CD workflow and Docker…#3560
Open
pedrofrxncx wants to merge 1 commit into
Open
Enhance npm tarball propagation handling in CI/CD workflow and Docker…#3560pedrofrxncx wants to merge 1 commit into
pedrofrxncx wants to merge 1 commit into
Conversation
…file. Update the release workflow to wait for the npm tarball instead of the version manifest, ensuring successful package installation. Modify Dockerfile to retry package installation with exponential backoff to accommodate CDN propagation delays.
Contributor
🧪 BenchmarkShould we run the Virtual MCP strategy benchmark for this PR? React with 👍 to run the benchmark.
Benchmark will run on the next push after you react. |
Contributor
Release OptionsSuggested: Patch ( React with an emoji to override the release type:
Current version:
|
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
1 participant
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.
…file. Update the release workflow to wait for the npm tarball instead of the version manifest, ensuring successful package installation. Modify Dockerfile to retry package installation with exponential backoff to accommodate CDN propagation delays.
What is this contribution about?
Screenshots/Demonstration
How to Test
Migration Notes
Review Checklist
Summary by cubic
Make npm publish propagation reliable in CI and Docker builds. The release workflow now waits for the
decocmstarball on the npm CDN, and the Dockerfile retries installation to avoid 404s right after publish.decocmstarball URL (not the version manifest) before building the Docker image.bun add decocms@$MESH_VERSIONwith simple backoff (10 attempts, 15s delay) to absorb CDN lag.Written for commit 326267d. Summary will update on new commits.
Review in cubic