Repository navigation
Commit fccb9ab
chore: depend on released cache and mongo instead of patching vendor
The Dockerfile cloned utopia-php/monorepo and utopia-php/mongo at fixed
commits and copied their src/ over vendor/, driven by build args pinned in
the workflow:
UTOPIA_CACHE_REFERENCE=d7c0806f...
UTOPIA_MONGO_REFERENCE=daea8f82...
That was a vendor patch standing in for releases that did not exist yet.
Both now do, so the lock resolves them normally and the machinery goes.
utopia-php/cache 4.0.1 -> 4.0.2 source 92e02dab6
utopia-php/mongo 1.5.2 source 20f9a644a
Both lock references equal the Packagist source references exactly, and
each release contains the pinned commit: d7c0806f is an ancestor of the
cache/4.0.2 tag commit, and 1.5.2 contains daea8f82.
Constraints already admitted these (cache ^4.0.0, mongo 1.*), so only the
lock moved. Removing the build args also stops a Docker build fetching
arbitrary external git refs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent d875e11 commit fccb9ab
3 files changed
Lines changed: 8 additions & 28 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | 28 | | |
32 | 29 | | |
33 | 30 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
4 | | - | |
5 | | - | |
6 | 3 | | |
7 | 4 | | |
8 | 5 | | |
| |||
13 | 10 | | |
14 | 11 | | |
15 | 12 | | |
16 | | - | |
17 | | - | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
| 13 | + | |
31 | 14 | | |
32 | 15 | | |
33 | 16 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments