Historical GenAIops rename migration

This is an existing-user reference for the historical 0.0.10 rename, not the current installation quickstart. New users start here.

Version 0.0.10 renamed the CLI, Python package, configuration namespace, environment variables, and generated state from GenAIops to Actspan.

Before you begin

Keep a backup of your workspace, environment files, lockfile, and local state. Retain the previous CLI environment if you need to inspect historical runs or finish paused workflows. This release does not include an automatic migration command or compatibility aliases for the old names.

For existing self-hosted installations, follow the deployment-specific upgrade instructions before restarting services. Existing portal workspace identity seeds and stored Git credential keys retain compatibility so the rename does not split workspace history or expose Git credentials to workflow runtimes. New credential writes use the Actspan names. These exceptions do not migrate local CLI evidence.

Obtain the Actspan binary or supplied package using the installation guide. An Actspan release or Python distribution must be published separately; changing the source does not make pip install actspan or a release download available. Developers maintaining an editable checkout must refresh their development environment against the renamed package; an existing installed genaiops command still refers to the old version.

Expected result for the current public download: actspan --version reports 0.2.0, updated configuration validates, and new runs write evidence under .actspan/.

Update configuration and integrations

Update authored YAML, Python imports and tool entrypoints, shell scripts, CI variables, and deployment configuration together. For example:

actspan:
  required_version: ">=0.2.0,<0.3"

Review and copy the settings you need from .genaiops.env into .actspan.env, renaming only the product-owned variables. Provider credentials such as OPENAI_API_KEY keep their names. Keep credentials out of Git. Review explicit paths and environment-variable references in configuration as well as variable names. The new defaults do not discover old environment or state directories.

Custom provider packages must publish the new plugin entry points and use compatible Actspan imports. Install the matching supplied provider artifact or source package when it is not available from your configured package index. Regenerate the lockfile with the new provider identities after reviewing the workspace; copying an old lockfile does not convert its package identities.

Preserve historical evidence

Keep old .genaiops/ state and .genaiops.lock.yaml as an archive. Start new Actspan state after updating configuration. Existing files are left in place; their presence does not import previous runs into the new ledger.

Old records can contain genaiops evidence/schema identifiers, provider package names, object names, and absolute paths. New records use the corresponding Actspan names. Copying a state directory alone does not guarantee that inspection, replay, or paused-workflow continuation will work. Use the previous CLI and its environment for historical records until a tested converter is available. Do not bulk-replace strings inside historical evidence: that can invalidate stored hashes, signatures, and revision relationships.

Validate the updated workspace

From the directory containing the updated workspace and environment file:

actspan init workspace.yaml
actspan validate workspace.yaml
actspan preview workspace.yaml

Review the new .actspan.lock.yaml and provider selections. Initialization prepares dependencies; validation and preview do not execute a model. Run one known workflow and inspect its new run ID before updating production automation.

Repository URLs and existing checkout folder names are separate from the product name. Keep the existing senatechnologies/genaiops, genaiops-examples, and genaiops-site hosted destinations until those repositories are renamed.