Repository navigation
backmesh v0.3.4
Upgrade with backmesh upgrade; there's no need to uninstall. With AWS or Azure runners, upgrade asks you to confirm the new VM types: run backmesh upgrade --plan, then backmesh upgrade --plan-id <id>.
Changes
installfinds your org. Without--org, it offers the org of the repo you're in, or lists the orgs you're an admin of to pick from. Without a terminal it prints the exact command to run. Your AWS CLI no longer needs a default region.- Runners use a fixed set of US regions. backmesh uses every US region on each cloud that offers all its VM types, and keeps the ones your account allows, naming any it skips.
--runnersnow takes clouds only, such as--runners aws;aws:us-east-2is no longer accepted. - Faster VM types first. Each label now tries m8i on AWS, n2 on GCP and D4ads_v5 on Azure first; m6i is no longer used.
- Cues land more often. A cued runner is timed for a slower-than-typical boot and waits up to 3 minutes for a late push, a re-cue keeps or replaces it cleanly, and cues work right after the listener restarts or upgrades.
Images, signed with cosign keyless by this repository's workflows:
- runner:
ghcr.io/anycloud-sh/backmesh-runner@sha256:9a221d3f20f6428900e2bd1ec04380cfdfd943ffaef93b7fa86c571e2c5327f5 - listener:
ghcr.io/anycloud-sh/backmesh-listener@sha256:a7e4e3801a5f27d00005259adc344b7eed84bdc0ae3ae53fe55d00d6a76ff5a0
Verify each with:
cosign verify ghcr.io/anycloud-sh/backmesh-runner@sha256:9a221d3f20f6428900e2bd1ec04380cfdfd943ffaef93b7fa86c571e2c5327f5 --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.3.4 --certificate-oidc-issuer https://token.actions.githubusercontent.com
cosign verify ghcr.io/anycloud-sh/backmesh-listener@sha256:a7e4e3801a5f27d00005259adc344b7eed84bdc0ae3ae53fe55d00d6a76ff5a0 --certificate-identity https://github.com/anycloud-sh/backmesh/.github/workflows/image.yml@refs/tags/v0.3.4 --certificate-oidc-issuer https://token.actions.githubusercontent.comPins anycloud 0.1.77; each CLI binary embeds compatibility.json, which backmesh upgrade reads. checksums.txt holds their sha256 digests.