Skip to content

feat: move the packages onto the v0.6.0-rc4 language - #6

Merged
slepp merged 7 commits into
mainfrom
feat/rc4-consumer-source
Sep 30, 2026
Merged

slepp merged 7 commits into
mainfrom
feat/rc4-consumer-source

Conversation

@slepp

@slepp slepp commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Why

Every package source on main fails to check against the v0.6.0-rc4 release: member separators, builtin variant spelling and actor lifecycle verbs have all moved. CI also could no longer start its S3 service because the quay.io MinIO images stopped pulling anonymously.

What

Rewrites the packages, suites and examples in the rc4 surface. Connection actors release their resources in #[on(stop)], so a call after stopped reports ActorError.Dead and the suites assert that. CI, the publish workflow and hew-cabi are pinned to the v0.6.0-rc4 tag, std is placed where the rc4 compiler looks for it, and MinIO comes from the pgsty builds.

Test

The corpus gate (check, suites, service-backed suites, native suites) and the native crate tests pass in CI against a source build of the tag. Locally, every source checks warning-free and the suites pass with the released rc4 binary.

The upstream quay.io MinIO images no longer pull anonymously, so the S3 service could not start. The pgsty builds are the maintained community distribution of the same server and client.
The rc4 compiler resolves std beside its profile directory, so the CI, publish and local toolchain layouts copy std there.
@slepp
slepp merged commit a32b781 into main Sep 30, 2026
2 checks passed
@slepp
slepp deleted the feat/rc4-consumer-source branch September 30, 2026 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant