Versions

Every Magmell deployment has a handler name and an explicit version string. Together they identify one immutable active build.

Choose meaningful versions

Version strings are application-defined. Simple integers work well for an early project:

magmell deploy ./reviewer --name reviewer --version 1 --wait
magmell deploy ./reviewer --name reviewer --version 2 --wait

Semantic versions or build identifiers are also valid when they match your release process:

magmell deploy ./reviewer --name reviewer --version 2.1.0 --wait

Magmell does not infer ordering from the string. “Latest” means the most recently created active deployment for that name, not the greatest semantic version.

Test a version explicitly

After deploying a candidate, pin test runs to it:

magmell run reviewer --version 2 --input-file fixture.json --wait

Runs without --version continue to resolve by the current latest active deployment:

magmell run reviewer --input-file request.json --wait

This makes explicit version selection appropriate for verification and default name selection appropriate for normal traffic.

Configure version-specific secrets

Secrets do not carry over. Configure the candidate independently:

await magmell.putSecretsByName(
  'reviewer',
  { MODEL_API_KEY: process.env.MODEL_API_KEY! },
  { version: '2' },
)

Then run that same selected version. Passing the version to both operations prevents accidentally changing whichever deployment is currently latest.

Historical runs stay identifiable

Run numbers belong to the handler name rather than an individual version. reviewer#57 continues to identify the same run after additional versions are deployed. Run detail records the deployment version used for that invocation.

Deleting a deployment

A deployment cannot be deleted while it is building or while it has non-terminal runs. Deletion archives its database record and removes it from normal active resolution; existing run history continues to point to the archived deployment.

You may later create the same name and version again, but it is a new deployment with a new ID and must receive its own secrets.