You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 59ce37e
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: COMPATIBILITY.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,27 @@
2
2
3
3
The migration preserves Docker Compose parsing, stack event names, generated stack fields, service labels, catalog question data, upgrade and rollback payloads, and compatibility API behavior.
4
4
5
+
The v0.14.40 candidate adds one server-private mode,
6
+
`compose-executor.real --catalog-launch-preview`, with fixed inspect/finalize
7
+
JSON contracts and bounded stdin/stdout. Existing parser, conversion, service
8
+
factory, launch-config and secret-reference owners produce the exact graph;
9
+
there is no second renderer or model-supplied URL/file/command interface.
10
+
Typed templates use the reviewed bounded subset and freeze the approved bytes.
11
+
12
+
Only a trusted Engine event may carry `catalogLaunchDelegation`. Its event-local
13
+
client uses the fixed delegation header for schema/read/transform/child calls;
14
+
missing or invalid proof cannot fall back to service FULL. Control progress and
15
+
replies retain the original trusted service channel, and unmarked ordinary
16
+
events retain their original client and API behavior. The Engine must recheck
17
+
the original actor/Key, source/plan/Stack/event/graph, destination create/update
18
+
and references on each request. Completion needs its committed ledger, full
19
+
intended links and normal deployment readiness, not only a Stack reply.
20
+
21
+
KVM, unsupported provider/host/build/file/dependency/network graphs, external or
22
+
cross-Stack links and unsupported typed inputs fail closed in this private mode;
23
+
they remain pending typed adapters rather than completed UI features. Component
24
+
source/unit and official CI evidence do not establish matching Server runtime.
25
+
5
26
The archived external Compose implementation is no longer a build dependency. The conversion, collection-copy, logger, and Compose configuration-hash contracts still required by this compatibility client are implemented locally and covered by behavior tests. This does not expand or silently reinterpret the accepted Compose document format.
6
27
7
28
`platform-compose.yml`, `PLATFORM_URL`, `PLATFORM_ACCESS_KEY`, and `PLATFORM_SECRET_KEY` are preferred. The historical companion filename, legacy CLI alias, `RANCHER_*` and `CATTLE_*` variables, `io.rancher.*` labels, generated `RancherCompose` and `RancherClient` types, legacy service-image identifiers, and vendored `github.com/rancher/*` paths remain only as wire, data, or dependency contracts.
Copy file name to clipboardExpand all lines: README.md
+17-3Lines changed: 17 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,20 @@ PastureStack is an independent community effort to preserve, audit, and moderniz
10
10
11
11
The maintained source uses Ubuntu 26.04, Go 1.27.3, and Python 3.14.9 for integration-source verification. Ubuntu build packages, the base image, and Go archives are fixed by snapshot, exact version, and SHA-256. Go dependencies are managed by `go.mod` and a reproducible module vendor tree. AWS access uses AWS SDK for Go v2; container structures use the maintained Moby API module; the command parser uses urfave/cli v3. The abandoned AWS SDK v1, Rancher generated-client modules, event-subscriber module, `docker/libcompose`, and other GOPATH-era dependencies have been removed. The small Rancher 1.6 protocol boundary retained by this compatibility CLI is maintained and tested locally. The Dapper builder does not embed a Docker CLI or mount a Docker socket; Docker is required only on the host to create and run the isolated builder. The maintained binaries are `pasturestack-compose` and `compose-executor`; `platform-compose.yml` is the preferred companion file. Releases are built and verified from the preserved source history; this repository does not enable automated deployment.
The matching Engine owns the original actor/Key ceiling, human approval,
23
+
encrypted inputs, exact graph and child-request ledger. Neither a component
24
+
build nor a Stack reply proves workload success. This candidate is unpublished;
25
+
official gates and complete matching Server runtime acceptance are pending.
26
+
13
27
## Configuration
14
28
15
29
Use `PLATFORM_URL`, `PLATFORM_ACCESS_KEY`, and `PLATFORM_SECRET_KEY`. Historical `RANCHER_*` and `CATTLE_*` settings remain compatibility fallbacks. Operator messages support `PASTURESTACK_LOCALE=en-US` and `zh-TW`.
@@ -31,7 +45,8 @@ publishes `compose-executor-0.14.39-linux-amd64.gz`. Published tags and assets
31
45
remain immutable; a later recipe or documentation commit does not replace
32
46
their bytes or change their producer identity.
33
47
34
-
Set `VERSION_OVERRIDE=0.14.39` for this recipe. Source changes alone are not
48
+
Set `VERSION_OVERRIDE=0.14.40` to verify this candidate; rebuild the published
49
+
release only from its numeric tag and original recipe. Source changes alone are not
35
50
publication proof: verify the official release assets and their SHA-256.
36
51
Component publication and matching Server acceptance are separate evidence
37
52
boundaries. The Python integration suite must run against an
@@ -66,6 +81,5 @@ proof; this is not a kernel or runtime exemption. Ubuntu security micro-updates
66
81
apply only to already-installed packages without changing the Python ABI.
67
82
68
83
The focused `Builder full-severity security` workflow validates builder-only
69
-
maintenance without rebuilding or republishing the unchanged `v0.14.39`
70
-
runtime. Raw distro pip metadata is retained alongside the actual replaced seed
84
+
maintenance without rebuilding or replacing published runtime assets. Raw distro pip metadata is retained alongside the actual replaced seed
71
85
paths, wheel hash, and existing narrow pip-vendor VEX evidence.
0 commit comments