Skip to content

docs: align Engine331 README with published artifact #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chen21019 merged 1 commit into from
Oct 2, 2026
Merged

docs: align Engine331 README with published artifact #71

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 22 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,29 @@ preserved upstream boundary.

## Current release

`v0.183.331` is being prepared to correct the stopped-container mapping condition
in 330. The common selection/update predicate will accept only running/active
The published release `v0.183.331` corrects the stopped-container mapping condition
in 330. The common selection/update predicate accepts only running/active
or stopped/inactive pairs; all source-account, unique-mapping, managed-container
and full-row compare-and-swap guards remain intact. Publication and consuming
Server/browser acceptance are pending. See the
[331 preparation note](docs/releases/orchestration-engine-0.183.331.md).

The published release `v0.183.330` is a narrowly scoped imported-container
and full-row compare-and-swap guards remain intact. See the
[331 release note](docs/releases/orchestration-engine-0.183.331.md) and
[immutable numeric release](https://github.com/PastureStack/orchestration-engine/releases/tag/v0.183.331).
The signed annotated tag binds exact CI source
`515a5d37a1194f827bc3ffde34db729905ecb2b1`; PR70 was normally merged as
`3249e77c149fb5220022baea01655dbe197c19e4` with an identical tree.
The WAR is `87,700,088` bytes, SHA256
`0c8310d9e9a872589972658d2fd8cb88f59f473ab8072a4746df5b0f4ef9e70e`.
Exact-source build 36972340448 passed 268 suites / 1,144 tests, zero failures,
errors or skips (22 native-name and six frozen-role response cases).
Six exact CI assets and three anonymous content readbacks passed; the exact
WAR also completed isolated JDK25.0.3 / H2 startup, with no network, exposed
ports or platform-data mounts. Artifact/build-image Critical and High findings
are zero; CodeQL 36972340453 retains four lower-severity findings. These scoped
checks do not claim zero risk, complete resource/role acceptance or Server500
and real-host/browser acceptance; the latter remain separate and pending.

## Historical 0.183.330 release

The previous release `v0.183.330` is a narrowly scoped imported-container
name refresh. A ping's UUID/name hint is never written as the authoritative
name: the Engine inspects the exact full Docker ID through its existing Agent
contract, and performs a name-only compare-and-swap on an eligible existing
Expand Down
28 changes: 23 additions & 5 deletions docs/releases/orchestration-engine-0.183.331.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Orchestration Engine 0.183.331

Preparing only. No official CI, release artifact, consuming Server image or
browser acceptance is claimed yet. Existing numeric tags remain immutable.
Published immutable numeric release. Consuming Server image and real-host/browser
acceptance remain separate and pending; existing numeric tags remain immutable.

## Root cause and minimal correction

Expand Down Expand Up @@ -35,9 +35,27 @@ not a real database compare-and-swap race or native browser acceptance claim.
The source-generated SELECT SHA-256 is
`07c2f72bfdc380df2d8bd706bf20769f98d75ab764da330b8ade5f66af61e1a8`.

Normal release CI must retain all ten DAO cases plus the nine handler, three
monitor and existing role-schema cases and the generated SELECT. The exact
CI WAR must be published and consumed by a new immutable Server, then checked
## Official release evidence

Signed tag `v0.183.331` binds exact source
`515a5d37a1194f827bc3ffde34db729905ecb2b1`. PR70 merged normally as
`3249e77c149fb5220022baea01655dbe197c19e4` with the same source tree.
Build/security run 36972340448 passed 268 suites / 1,144 tests, with zero
failures, errors or skips. All ten DAO, nine handler, three monitor and six
retained role-schema cases passed; the production SELECT matches the 84-case
MariaDB fixture above.

WAR SHA256 `0c8310d9e9a872589972658d2fd8cb88f59f473ab8072a4746df5b0f4ef9e70e`,
87,700,088 bytes. Six exact CI assets are published; checksum, source revision
and test-results contents also passed anonymous readback. The exact WAR exited
0 in isolated JDK25.0.3 / H2 startup, without network, exposed ports, Docker
socket or platform data. Artifact/build-image Critical and High findings are
zero. CodeQL run 36972340453 retains four lower-severity findings; this does
not imply an all-findings-zero scan or full permissions acceptance.

The initial candidate's pre-build gate failure is retained: three expected
330 version/log lines were corrected to 331 without relaxing any checks.
The exact CI WAR must be consumed by a new immutable Server, then checked
on the real QA host and native browser before declaring name acceptance.
Keep existing environment variables, volumes, AppArmor, restart policy,
HTTPS origin, OIDC/MFA/session ownership and nftables unchanged. Rollback uses
Expand Down
Loading