Markata naming migration

The Go static site generator formerly known as markata-go is now Markata. The repository rename is complete, but Markata remains on the 0.x release line; the name change does not imply a 1.0 release. The original Python implementation is now at WaylonWalker/markata-py.

What works now

New development builds provide the preferred markata executable. The legacy markata-go command remains supported, including existing tagged downloads. The official install script attempts a canonical archive and falls back to a legacy release where needed, installing both command names. If a different application (including Python Markata) already owns the markata command at the destination, the installer stops rather than overwriting it. Move the conflicting executable or choose a separate install directory.

curl -sSL https://raw.githubusercontent.com/WaylonWalker/markata/main/install.sh | bash
markata --help
markata build

# Existing automation still works:
markata-go build

If you install from Go source rather than binary releases, the new command is available from main until the first tagged version with the new entry point:

go install github.com/WaylonWalker/markata/cmd/markata@main

Configuration stays as-is for now

There is no immediate need to rename configuration:

# markata-go.toml remains correct during the compatibility window
[markata-go]
output_dir = "output"

MARKATA_GO_OUTPUT_DIR, MARKATA_GO_SITE_DIR and other existing MARKATA_GO_* overrides continue working. Configuration overrides applied by the Go config loader also accept the canonical MARKATA_* aliases, for example MARKATA_OUTPUT_DIR. The canonical name takes precedence if both are set; conflicting values record name_migration_warnings on the loaded config (without exposing the values). Other runtime-specific settings may still use legacy names; migrate those only after their individual support is verified.

Renaming the config file to markata.toml or the TOML section to [markata] is not yet supported by the Go CLI, and may be confused with an original Python Markata configuration. Keep existing TOML filenames/sections for now.

For the installer, MARKATA_INSTALL_DIR and MARKATA_VERSION are preferred; the legacy MARKATA_GO_INSTALL_DIR and MARKATA_GO_VERSION still work.

GitHub repository cutover completed

The repository swap was completed on October 18, 2026. The Go implementation is now WaylonWalker/markata (repository ID 1140034778); the original Python implementation is WaylonWalker/markata-py (repository ID 333449359). The old Go GitHub URL may redirect to the canonical Go repository, but use the new URL explicitly in new automation. Old Python bookmarks targeting WaylonWalker/markata now land on Go.

Read the repository cutover runbook for the owner rename checks and post-cutover infrastructure audit. The GitHub rename alone does not migrate the Go module import path, Python PyPI ownership, legacy configuration names, container registry permissions, or live sites.

Package and production migration

The Go module now declares github.com/WaylonWalker/markata, and tracked Go imports have migrated to that path. Pinned pre-cutover releases may still be available under the old github.com/WaylonWalker/markata-go module identity. Avoid mixing both module paths in a single dependency graph. For new Go code and go install, use github.com/WaylonWalker/markata. See the Go module cutover guide for migration details.

Existing markata-go.toml, [markata-go], MARKATA_GO_*, markata-go binaries and legacy GHCR builder references are intentionally preserved. Do not rename Kubernetes PVCs, Helm release names or secrets merely to match branding. Audit Argo CD chart repo URLs and permissions separately, and verify published image compatibility and live workloads before changing production images. No new release tag is implied by the rename.