Skip to content

Releases: itsjustayush/beton-cli

Beton CLI v0.5.0 — npm distribution channel

Choose a tag to compare

@itsjustayush itsjustayush released this 19 Aug 10:11

Beton CLI v0.5.0 — npm distribution channel

Beton CLI v0.5.0 adds an official npm distribution wrapper so users can install the local-first command layer with one command:

npm install -g beton-cli

Highlights

  • Added the beton-cli npm package with the beton executable.
  • Added a cross-platform postinstall bootstrap that downloads the matching official GitHub source release, creates an isolated Python virtual environment, installs Beton and its runtime dependencies, and exposes the command globally.
  • Added Windows-safe behavior that works from ordinary PowerShell or Command Prompt without requiring Activate.ps1, a VS Code terminal, or a permanent execution-policy change.
  • Added npm-aware beton version --upgrade support for npm-installed instances while preserving the guarded Git-based upgrade flow for source checkouts.
  • Added npm-specific README and bundled MIT license files.
  • Updated the main README, landing page, deployed documentation, package metadata, examples, and changelog to v0.5.0.

Requirements

The npm channel requires Node.js 18+, npm, and Python 3.10+. Git is not required for the npm installation path. Beton remains a local Python CLI and is intentionally not published as a PyPI package.

Author

Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.4.3 — Reliable Tag-Checkout Upgrades

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 16:58

Beton CLI v0.4.3 — Reliable Tag-Checkout Upgrades

Beton CLI v0.4.3 fixes the automatic upgrade path for users who installed from an official release tag.

Fix

When a user clones a tagged release and runs git fetch --tags origin, Git may have the tag commit locally without creating the origin/main remote-tracking reference. Previously, beton version --upgrade attempted to check out origin/main and failed with:

fatal: 'origin/main' is not a commit and a branch 'main' cannot be created from it

v0.4.3 explicitly fetches the main branch into refs/remotes/origin/main before switching the detached release checkout to the update branch.

Included updates

  • Fixed beton version --upgrade for detached official release-tag checkouts.
  • Added regression coverage for the explicit remote-tracking branch fetch.
  • Updated package metadata, README, changelog, landing page, and deployed documentation to v0.4.3.
  • Preserved the clean-tree, official-remote, confirmation, dry-run, fast-forward, and rollback safeguards.

Verification

  • All 18 tests passed.
  • Python compilation passed.
  • Production website build passed.
  • BETON 0.4.3 version output verified.
  • Stale v0.4.2 current-surface references checked.
  • git diff --check passed.

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.4.2 — Simplified Windows Workflow

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 15:54

Beton CLI v0.4.2 — Simplified Windows Workflow

Beton CLI v0.4.2 makes the Windows experience easier to use from PowerShell and VS Code.

Improvements

  • Added a one-command Windows installer:

    powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\install.ps1
  • The installer creates the virtual environment, installs Beton in editable mode, creates a user-level %USERPROFILE%\bin\beton.cmd shim, and adds it to the user PATH.

  • Added -NoPath for users who prefer the direct .venv\Scripts\beton.exe workflow.

  • Removed the need to activate Activate.ps1 in the recommended setup.

  • Improved Windows resolution for common chrome, code, and spotify installations.

  • Added clearer beton help guidance: beton alone shows the brand screen, while beton beton is invalid.

  • Added Windows Chrome path-resolution test coverage.

  • Updated README, changelog, landing page, and deployed documentation to v0.4.2.

Recommended Windows setup

Set-Location C:\path\to\beton-cli
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\install.ps1

Open a new VS Code or PowerShell terminal, then run:

beton doctor
beton --version
beton version --upgrade

Verification

  • All 17 CLI and unit tests passed.
  • Python compilation passed.
  • Production website build passed.
  • BETON 0.4.2 verified.
  • beton help guidance verified.
  • Windows path-resolution coverage passed.
  • git diff --check passed.

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.4.1 — Windows-Safe Source Installation

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 14:24

Beton CLI v0.4.1 — Windows-Safe Source Installation

Beton CLI v0.4.1 fixes the Windows installation path reported by users cloning the official source release.

Fixes

  • Removed mandatory PowerShell virtual-environment activation from the recommended Windows workflow.
  • Added direct .venv\Scripts\python.exe and .venv\Scripts\beton.exe commands that work without changing PowerShell execution policy.
  • Updated scripts/install.ps1 to use the Python launcher when available, fall back to python, and provide a clear installation message when Python is missing.
  • Added explicit Python 3.10+ and PATH guidance for Windows, including the py/python not-found case.
  • Added direct Windows examples for beton version --upgrade, --yes, and --dry-run.
  • Clarified that Git’s annotated-tag warning during a successful shallow clone is nonfatal when Git exits successfully and switches to a commit.
  • Updated README, changelog, landing-page metadata, and deployed documentation to v0.4.1.

Recommended Windows workflow

git clone --branch v0.4.1 --depth 1 https://github.com/itsjustayush/beton-cli.git
Set-Location beton-cli
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .
.\.venv\Scripts\beton.exe doctor

If py and python are not recognized, install Python 3.10+ from python.org and enable Add python.exe to PATH.

Verification

  • All 16 CLI tests passed.
  • Python compilation passed.
  • Production website build passed.
  • BETON 0.4.1 version output verified.
  • Windows command syntax and direct executable paths reviewed.
  • git diff --check passed.

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.4.0 — Safe Source-Checkout Upgrades

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 14:11

Beton CLI v0.4.0 — Safe Source-Checkout Upgrades

Beton CLI v0.4.0 adds a safe, source-aware upgrade workflow so official GitHub checkouts can update themselves without a manual reinstall.

Highlights

  • Added beton version as a read-only subcommand that reports the installed version.
  • Added beton version --upgrade to update an official itsjustayush/beton-cli checkout from GitHub.
  • Added confirmation by default and --yes for explicit non-interactive confirmation.
  • Added beton --dry-run version --upgrade to preview the operation without modifying the checkout.
  • Restricted automatic updates to the official repository, the main branch, or an official detached release checkout.
  • Refused to overwrite uncommitted changes and used fast-forward-only synchronization.
  • Refreshed the active Python environment from the updated editable source checkout.
  • Added rollback to the previous commit if environment refresh fails.
  • Documented the editable installation requirement and upgrade workflow in the README and deployed documentation.

Usage

beton version
beton version --upgrade
beton version --upgrade --yes
beton --dry-run version --upgrade

For automatic upgrades to work, install BETON from the official GitHub source checkout in editable mode:

git clone --branch v0.4.0 --depth 1 https://github.com/itsjustayush/beton-cli.git
cd beton-cli
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e .
beton doctor

Verification

  • python -m compileall -q src passed.
  • All 16 CLI tests passed.
  • beton --version reports BETON 0.4.0.
  • Real clean-checkout dry-run passed.
  • Real confirmed no-op upgrade passed.
  • Production website build passed.
  • git diff --check passed.

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.3.4 — Corrected Source Installation and Documentation

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 13:02

Beton CLI v0.3.4 — Corrected Source Installation and Documentation

Beton CLI v0.3.4 synchronizes the package metadata, README, changelog, landing page, and deployed documentation with the actual implementation and official distribution model.

Highlights

  • Clarified that Beton is not currently distributed as a PyPI package.
  • Added official GitHub source-install instructions pinned to the v0.3.4 release for Linux/macOS and Windows PowerShell.
  • Clarified that pip is used only as the local build installer for the cloned source tree.
  • Updated package metadata and beton --version to 0.3.4.
  • Added canonical repository, documentation, and release URLs to pyproject.toml.
  • Synchronized the README, changelog, landing-page release labels, documentation version labels, and installation examples.
  • Retained the complete command reference and the separated PowerShell installation and troubleshooting panels.

Installation model

Beton should be obtained from the official GitHub repository and its tagged release:

git clone --branch v0.3.4 --depth 1 https://github.com/itsjustayush/beton-cli.git
cd beton-cli
python3 -m venv .venv
source .venv/bin/activate
python -m pip install .
beton doctor

Windows PowerShell users should activate the virtual environment with .\.venv\Scripts\Activate.ps1 before running python -m pip install ..

Verification

  • Production website build passed.
  • All 14 CLI tests passed.
  • Clean virtual-environment installation passed.
  • beton --version reports BETON 0.3.4.
  • beton --dry-run open https://github.com completed successfully.

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.3.3 — Documentation Route Alias

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 12:29

Beton CLI v0.3.3 — Documentation Route Alias

This patch release adds /docs as a convenient alias for the canonical /documentation route.

Changes

  • Added a lightweight docs.html redirect entry.
  • Included the alias in the Vite multi-page build.
  • Preserved /documentation as the canonical public URL while making /docs available as a shorter alternative.

Release provenance

  • Tag target: d4a65614b1f06c50c2db0408692399d8b16b3a7e
  • Commit: Add clean docs route alias
  • Release type: Patch release

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.3.2 — Canonical Documentation Route

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 12:29

Beton CLI v0.3.2 — Canonical Documentation Route

This patch release replaces the space-containing documentation filename with a clean, production-friendly /documentation route.

Changes

  • Renamed the documentation entry to documentation.html for clean deployment URLs.
  • Updated the Vite multi-page build configuration to use the new entry.
  • Updated landing-page links to point to /documentation.
  • Added Vercel routing for the canonical documentation path.

Release provenance

  • Tag target: 7bf77c87d110bbfa7d925f5fbdb6efd1c630d098
  • Commit: Serve docs at clean documentation route
  • Release type: Patch release

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.3.1 — Documentation Navigation

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 12:29

Beton CLI v0.3.1 — Documentation Navigation

This patch release connects the main landing page and the documentation experience into a navigable product surface.

Changes

  • Added prominent documentation links to the landing-page navigation, hero actions, implementation section, and footer.
  • Added a back-to-landing-page link in the documentation header.
  • Kept the documentation page and landing page cross-linked for straightforward navigation.

Release provenance

  • Tag target: c03340e26a38bde0543875080612b35a76956bd4
  • Commit: Link landing page to CLI documentation
  • Release type: Patch release

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com

Beton CLI v0.3.0 — Complete CLI Documentation

Choose a tag to compare

@itsjustayush itsjustayush released this 18 Aug 12:29

Beton CLI v0.3.0 — Complete CLI Documentation

Beton CLI v0.3.0 introduces the project’s first comprehensive documentation experience. It makes the command surface, configuration model, guides, and troubleshooting reference available as a dedicated static documentation page.

Highlights

  • Added the standalone Beton CLI Docs page with a Mintlify-inspired documentation layout.
  • Documented installation, quickstart workflows, every implemented command, global flags, settings, aliases, data storage, browser control, dry-run behavior, plain mode, and troubleshooting.
  • Added responsive navigation, on-page section tracking, search, copyable code blocks, theme switching, cards, tables, and safety callouts.
  • Configured the Vite build to emit the documentation page as a second static entry.

Release provenance

  • Tag target: 203962c4410bcf1ee6876ab8c8026d54be709f60
  • Commit: Add full Beton CLI documentation page
  • Release type: Minor feature release

Signed by
Ayush Bhattacharya
itsjustayush.vercel.app
info.cometlabs@gmail.com