Upgrade regorus to 0.11.0 - #224
Conversation
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
The alinux3 base image ships a cargo too old for the bumped MSRV 1.88 (regorus 0.11), causing PR #224 docker-build CI to fail. The base cargo also forced a `sed` downgrade of Cargo.lock v4 -> v3. Install rust via rustup (pinned to 1.88.0, matching rust-check.yml) in Dockerfile.as-grpc, Dockerfile.as-restful, Dockerfile.rvps, and Dockerfile.kbs, and drop the now-unnecessary lock-format downgrade. Co-Authored-By: Claude <noreply@anthropic.com>
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
regorus 0.11 needs Rust 1.88. Bump the MSRV to 1.88 and make every build path use a 1.88 toolchain: - CI (rust-check.yml) and workspace rust-version -> 1.88; propagate rust-version.workspace = true to all member crates. - alinux3 Dockerfiles (as-grpc/as-restful/kbs/rvps): drop the stale distro cargo and install rustup 1.88; remove the Cargo.lock v4->v3 downgrade hack it needed. - Dockerfile.rvds: rust:1.75 -> 1.88. - RPM buildspecs (alinux3/anolis23): install rustup 1.88 and pass --define 'with_rustup 1'; trustee.spec keeps a dual mode that falls back to system cargo/rust >= 1.88 when with_rustup is not set. - Add RVDS to the docker-build CI matrix. Also fix the clippy/rustc lints the 1.88 toolchain newly flags across eventlog/verifier/rvps/as/kbs. Co-Authored-By: Claude <noreply@anthropic.com>
Upgrade regorus 0.2.6 -> 0.11.0.
regorus 0.11 turns on rego.v1 by default and rejects the legacy
`allow { ... }` policy syntax, so call set_rego_v0(true) at the
attestation-service / kbs engine creation sites to keep existing
policies working. Includes the wasm fix for 0.11 and tests that pin
the rego.v0/v1 compatibility matrix.
Co-Authored-By: Claude <noreply@anthropic.com>
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
3 participants
This pr is the pre-work for #225. The main purpose is to upgrade workspace regorus crate from 0.2.6 to 0.11.0, which aligns to upstream.
One of the breaking change:- regorus 0.11 made the rego.v1ifkeyword required before rule bodies. So policy likeshould be rewrite toor it will failed in regorus 0.11.0.update: rego v0 syntax is compatible now.