Skip to content

The open-source agent harness - the runtime layer that turns an LLM into a working agent.

misc: Wait for npm to advertise package before Docker build (#804)

Bhavesh Patel6e3eac555141
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index fcfb4187f..2b701f955 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -235,13 +235,25 @@ jobs:
echo "published=true" >> "$GITHUB_OUTPUT"
echo "version=$VERSION" >> "$GITHUB_OUTPUT"
echo "Published @truefoundry/trueforge@$VERSION"
- sleep 30
else
echo "published=false" >> "$GITHUB_OUTPUT"
echo "version=" >> "$GITHUB_OUTPUT"
echo "@truefoundry/trueforge was not in this publish set"
fi
+ - name: Wait for npm to advertise package
+ if: steps.trueforge.outputs.published == 'true'
+ env:
+ VERSION: ${{ steps.trueforge.outputs.version }}
+ run: |
+ echo "Newly published npm packages are typically available in about five minutes, and may take up to 15 minutes or more at peak times."
+ echo "https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata/"
+ for _ in $(seq 30); do
+ npm view "@truefoundry/trueforge@$VERSION" version && exit 0
+ sleep 30
+ done
+ exit 1
+
# Sibling of npm publish (same gates). Skips when pyproject version is already on PyPI.
publish-python:
name: Publish Python SDK