Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Homeboy releases omit platform CLI archives

Open
  • Is something wrong?
#2,384 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
build-system, cli, release

Research direction

Start with scripts/package-release-artifact.ts and trace how the canonical Homeboy component declares and publishes release outputs. Compare its outputs with the WordPress extension's default managed-release archive names and run the release package coverage checks plus a fresh extension setup. Done means supported CLI archives contain accepted provenance and dependencies, and setup no longer falls back to a source install.

Written by the indexing model from the issue text.

Description

Problem

WP Codebox releases built through the canonical Homeboy component publish the WordPress plugin ZIP and npm workspace tarball, but omit the platform CLI archives that the WordPress extension's default managed-release setup consumes.

Observed after releases v0.24.1 and v0.24.2:

Installing WP Codebox CLI from managed release artifact wp-codebox-cli-linux-x64.tar.gz...
WP Codebox release artifact is unavailable from the configured authority; falling back to source install

The v0.24.2 GitHub release contains only:

  • wp-codebox.zip
  • wp-codebox-workspace-0.24.2.tgz

Yet scripts/package-release-artifact.ts already defines wp-codebox-cli-${platform}-${arch}.tar.gz, and the Homeboy WordPress extension defaults to releases/latest/download/wp-codebox-cli-${platform}-${arch}.tar.gz.

Impact

Every extension setup falls back to cloning, installing, and building WP Codebox from main. This is slower, loses immutable release-asset authority, and leaves the configured release path perpetually unavailable even though setup eventually succeeds.

Expected behavior

The canonical release publishes supported platform CLI archives as authoritative GitHub release assets, including at least wp-codebox-cli-linux-x64.tar.gz, with provenance that the managed WordPress installer accepts.

Acceptance criteria

  • Homeboy release packaging invokes the existing platform CLI artifact builder or otherwise declares its outputs as release assets.
  • Supported platform archive names match installer expectations.
  • Archives include accepted version/build provenance and the runtime packages required by the CLI.
  • Release package coverage verifies all declared CLI archives.
  • A fresh WordPress extension setup installs in managed release mode without source fallback.
Dominant language
TypeScript
Stars
17
Forks
4
Avg merge
1h 11m
Merged PRs (30d)
39

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/wp-codebox

All issues in Automattic/wp-codebox

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.