v0.0.1-alpha.27
Pre-releaseOvercast v0.0.1-alpha.27
Docker Images
Full image with the web management console:
- Pull:
ghcr.io/neaox/overcast:0.0.1-alpha.27 - Channel tag:
ghcr.io/neaox/overcast:alpha - Registry: overcast package
Headless slim image for CI pipelines:
- Pull:
ghcr.io/neaox/overcast-slim:0.0.1-alpha.27 - Channel tag:
ghcr.io/neaox/overcast-slim:alpha - Registry: overcast-slim package
docker run --rm -p 4566:4566 -p 4567:4567 ghcr.io/neaox/overcast:0.0.1-alpha.27
docker run --rm -p 4566:4566 ghcr.io/neaox/overcast-slim:0.0.1-alpha.27Native Binaries
Download a binary for your platform from the assets below and verify it with SHA256SUMS.
| Asset | SHA256 |
|---|---|
overcast-darwin-amd64 |
146c385f2362ebb984830f961866f92e5f957fb93e568674438494561c3dea6c |
overcast-darwin-arm64 |
636313589259988186984dd732184c83d47a803bbff8a1879310e306b1aa53aa |
overcast-linux-amd64 |
bbdca26919c9eb438acc94ac69f2c40cd5bd7c6c76d18969d997ce3ac68998e7 |
overcast-linux-arm64 |
135e10bdc40d98faac7db5caf88927adea0f3128c0595957410abe37eefb6f32 |
overcast-windows-amd64.exe |
636ef72268c7cd4c5e6a9629ba8e1fdc431f31f43de8a3f538ef380a6d3658c0 |
overcastd-darwin-amd64 |
d6173742dfeb1fd9a91c20c00cfee50c665cab0f73e17e523951b3894c254156 |
overcastd-darwin-arm64 |
08d4d127406a82b422c966a4b7b7c3c3ad1d2e35a4314ef410f90421c946706f |
overcastd-linux-amd64 |
35f96ad62cefffe0e52d02558fdfe954701081f30709068d78bc7129525fc644 |
overcastd-linux-arm64 |
527f630f75066a6c8601face8cb33650ad6520b09db12c8a55a1c8a1e5540e8f |
overcastd-windows-amd64.exe |
a3fa454c1031dd27540895b3db724446e9b2267c25e8103b107c3ccb5d780bc5 |
Release Notes
Changed
-
Release process (changelog) — unreleased changes are now recorded as one fragment file per PR under
.changelog/instead of direct edits toCHANGELOG.md's[Unreleased]section, which every concurrent PR used to merge-conflict over. CI lints the fragments and keeps[Unreleased]empty (scripts/changelog.py check); release prep assembles the fragments into the versioned section (scripts/changelog.py assemble), and the release gate fails if any fragment is left unconsumed. -
CI (release safety) — publishing now requires the maintainer's one-click approval: the release workflow's four publish jobs run in a
releaseenvironment with a required reviewer, so builds and tests stay unattended while nothing ships without a human seeing the exact SHA. Alongside the repository ruleset changes (required status checks, no bypass actors), routine merges no longer use--admin— the rules that were previously convention are now enforced, including on automation.
Fixed
- CloudFormation (stack updates) — stack updates no longer destroy live resources behind pinned names, and resources whose services reject duplicate creates can now actually be updated. Two related engine/handler defects: first, a replacement whose create is an upsert keyed by a pinned name handed back the original physical ID, and both the post-success cleanup and the rollback path then deleted that ID — destroying the one live resource behind a stack that reported
UPDATE_COMPLETE(confirmed with CloudWatch alarms); the engine now reports a same-ID replacement as an in-place update, which also makes the create-overwrite of every upsert-style service (Athena, Glue, Firehose, OpenSearch, MSK, ECS, WAFv2) the correct in-place behaviour. Second, pinned-name resources on services that 409 duplicate creates could not be updated at all, because replacement re-created the same name; their handlers now replace only on the properties real CloudFormation replaces on and apply the rest through the service's own update API (CloudWatchPutMetricAlarm, Route53UPSERT, EKSUpdateClusterConfig/UpdateClusterVersion/UpdateNodegroupConfig/UpdateAccessEntry/UpdatePodIdentityAssociation, TransferUpdateUser, PipesPATCH), while backup vaults, scheduler schedule groups, and the RDS/ElastiCache subnet groups — which have no modify operation — keep the live resource via a name-guarded identity update instead of a guaranteed 409.AWS::ECR::Repository, the original symptom, now updatesRepositoryPolicyTextand lifecycle rules in place instead of replacing on any property change, so re-runningcdk bootstrapafter a CDK upgrade succeeds instead of dying withRepositoryAlreadyExistsException, andGetAtt'sRepositoryUriis re-read from ECR so it reflects the registry this environment actually serves. Scheduler schedule groups with tags also create correctly now — CloudFormation-shaped tag lists were passed to the emulated API's map form, failing every tagged create. Replacement-on-any-change is deliberately kept where it is real CloudFormation behaviour (Shield, ACM, LaunchConfiguration, IAM AccessKey, EKS FargateProfile).
Release: https://github.com/Neaox/overcast/releases/tag/v0.0.1-alpha.27