A small record of progress.

Versioned releases, explicit upgrades, and a clear account of what changed.

v0.1.1 Startup migration fix

This compatibility release adopts existing EnvManager startup hooks in place, including source "$HOME"/.envmanagerrc. Supported HOME, braced HOME, and tilde forms retain their original command and startup position.

• Repair the duplicate initialization produced when v0.1.0 kept an unrecognized legacy hook and appended a managed block.
• Use one read-only planner for dry runs and migration. Dry runs report the startup file, line, and intended action.
• Stop before edits for unfamiliar active references, multiple legacy hooks, conflicting markers, or edited managed blocks.
• Check single invocation, original ordering, and repeat-install stability in Bash and Zsh using disposable fixtures.

Use the current installer to repair shell integration; an existing checkout is reused. --upgrade is only needed to update checkout code. Release v0.1.1 includes its manifest and checksums. Existing v0.1.0 downloads remain unchanged.

v0.1.0 Initial installer release

The first public installer release brings the existing EnvManager shell helpers together with a repeatable macOS/Linux setup flow and dedicated documentation.

• A POSIX installer with Bash/Zsh integration, custom directories, release pinning, dry runs, upgrades, and removal of managed integration.
• A core preset for fresh installations. Existing checkouts retain their module choices.
• Repeat-install checks, symlink and permission preservation, backups on changes, and verification of published Git commits.
• Explicit updates for release checkouts; the normal branch-based updater remains available to existing installations.
• Documentation for ordered path additions, MANPATH defaults, optional modules, local overrides, and cross-session concurrency.
• A static website with separate macOS and Linux installation pages, canonical URLs, social metadata, robots directives, and a sitemap.

See the tagged release for the release archive, installer, manifest, and SHA-256 checksums. Upgrade with the installer’s --upgrade option after preserving local changes in your checkout.

Follow the implementation

Individual changes and validation runs are recorded in the Git history and GitHub Actions. The documentation describes current behavior, including the distinction between core configuration and optional tool installation.