osborn 0.9.21 → 0.9.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/Dockerfile.sandbox +11 -2
- package/package.json +1 -1
package/Dockerfile.sandbox
CHANGED
|
@@ -16,8 +16,17 @@ RUN apt-get update -qq && \
|
|
|
16
16
|
python-is-python3 && \
|
|
17
17
|
rm -rf /var/lib/apt/lists/*
|
|
18
18
|
|
|
19
|
-
#
|
|
20
|
-
RUN npm install -g osborn@latest
|
|
19
|
+
# Pin osborn to an explicit version so Docker layer cache invalidates whenever
|
|
20
|
+
# the version changes. Earlier `RUN npm install -g osborn@latest` looked correct
|
|
21
|
+
# but it never invalidated: `latest` is a tag resolved by npm at install time,
|
|
22
|
+
# but Docker's layer cache keys on the literal RUN command string. So every
|
|
23
|
+
# rebuild reused the cached layer from when "latest" was a previous version,
|
|
24
|
+
# producing images labeled :0.9.21 that actually contained osborn 0.9.19 inside.
|
|
25
|
+
#
|
|
26
|
+
# Pass --build-arg OSBORN_VERSION=X.Y.Z when building. image-build-check.ts
|
|
27
|
+
# does this automatically using the npm-registry-resolved latest version.
|
|
28
|
+
ARG OSBORN_VERSION=latest
|
|
29
|
+
RUN npm install -g "osborn@${OSBORN_VERSION}" @anthropic-ai/claude-code
|
|
21
30
|
|
|
22
31
|
# Persistent workspace + claude config dirs
|
|
23
32
|
RUN mkdir -p /workspace /root/.claude
|