# mgf-cloud v0.1.0 — maiden release (no migration)

> **Audience:** anyone looking for a migration runway into
> `mgf-cloud` v0.1.0.
> **What this is:** there is **nothing to migrate.** `mgf-cloud` is
> a brand-new, greenfield library — its first published version is
> 0.1.0. This note exists so the `docs/cutover/` bucket has a
> record for the maiden release; it is **not** a breaking-change
> guide (per DOC-05, those only exist for releases that break a
> *previously published* documented surface).

## There is no prior surface

`mgf-cloud` was not extracted from another package and did not
exist before 0.1.0. There is no `mgf-common[cloud]` extra, no
predecessor module, and no earlier public API. Nothing to rewrite,
re-pin, or codemod.

## What 0.1.0 is

0.1.0 is the **conformant scaffold** — Pass 1 of the 7-pass build
tracked in
[`../inprogress/mgf-cloud-progress.md`](../inprogress/mgf-cloud-progress.md).
The buildable, gated, registered skeleton + the design docs ship
here; the surface that consumers actually use lands across the
later passes:

- the provider abstraction (`CloudProvider` + `FakeProvider`) — Pass 2;
- the Infomaniak (OpenStack) adapter — Pass 3;
- the `mgf-cloud` CLI — Pass 4;
- the local web GUI (`mgf-cloud web`) — Pass 5.

See [`../design/DESIGN.md`](../design/DESIGN.md) for the
architecture and [`../../README.md`](../../README.md) for what the
library provides.

## How to adopt 0.1.0

```toml
# pyproject.toml — pin tightly within the 0.x window (AP-03)
dependencies = ["mgf-cloud>=0.1,<0.2"]
```

Then install the extra for the provider you need (each keeps the
core light):

```bash
pip install 'mgf-cloud[infomaniak]'   # the Infomaniak (OpenStack) provider
pip install 'mgf-cloud[web]'          # the local web GUI
pip install 'mgf-cloud[remote]'       # SSH bootstrap (paramiko)
pip install 'mgf-cloud[s3]'           # S3-compatible object storage (boto3)
```

`mgf-*` siblings resolve from the Codeberg registry (PKG-06), not
pypi.org.

## When the first real cutover guide appears

The first time a release breaks a documented surface — a MINOR
within `0.x` per **AP-03**, or a MAJOR — a `v<X.Y.Z>.md` guide is
added alongside this one with the four mandatory DOC-05 sections
(what changed, the codemod recipe, the manual steps, the FEEDBACK
back-link). Until then, the [`CHANGELOG.md`](../../CHANGELOG.md) is
the full record.
