Skip to content

phase 2: stand up @stackbilt/build in new Stackbilt-dev/stackbilt-build repo #125

Closed

Description

@stackbilt-admin

Phase 2 of RFC #112 — relocate the commercial CLI surface (run, architect, scaffold, login) from @stackbilt/cli into a new @stackbilt/build npm package housed in a new GitHub repo.

Context

Scope

  1. Create the repo Stackbilt-dev/stackbilt-build (public, Apache-2.0).
  2. Port files from @stackbilt/cli:
    • packages/cli/src/commands/{login,architect,run,scaffold}.ts
    • packages/cli/src/credentials.ts, http-client.ts
    • packages/cli/src/types/scaffold-contract-types.ts (vendored)
    • Tests: credentials.test.ts, login.test.ts, auth-wiring.test.ts
  3. Package naming: @stackbilt/build on npm, stackbilt bin alias.
  4. Replicate release infra: charter's release.yml with npm trusted-publisher OIDC (see ci(release): publish to npm on tag push #118 through ci(release): upgrade npm to 11+ for trusted-publisher OIDC auth #121 for the full end-state pattern; notably: npm 11+ upgrade step, no registry-url, no NODE_AUTH_TOKEN).
  5. Configure npm trusted publishers on @stackbilt/build before first publish.
  6. Initial version: resolve Open Q feat(setup): add docs/planning preset for non-code workspaces (ADX-006) #3 (start at 0.1.0 vs. match charter's current minor) before first publish.
  7. New repo README: reclaim the stackbilt run hero + scaffolding visuals that were removed from charter in docs: lead README with governance; remove build-hero + images #124.

Acceptance criteria

  • Stackbilt-dev/stackbilt-build repo exists, public, Apache-2.0.
  • @stackbilt/build on npm at initial version, installable globally.
  • stackbilt run "..." end-to-end against the engine, installed via the new package.
  • All tests pass in new repo's CI.
  • Release workflow uses OIDC trusted-publisher auth. Provenance attestations attached to published tarballs.

Out of scope (tracked separately)

  • Phase 3 — stronger CLI deprecation notice in charter.
  • Phase 4 — full removal of the 4 commands from @stackbilt/cli at Charter 1.0.

References

Activity

  1. stackbilt-admin commented on May 6, 2026

    @stackbilt-admin
    MemberAuthor

    Progress update (2026-05-06):\n\n- Created new repo: https://github.com/Stackbilt-dev/stackbilt-build (public, default branch).\n- This satisfies the "Create the repo" scope item and unblocks source-port + release-infra work.\n\nNext phase for #125:\n1. Port + credential/http client files into the new repo package skeleton.\n2. Stand up release workflow with npm trusted-publisher OIDC.\n3. Publish initial version and validate install + flow.

  2. stackbilt-admin commented on May 6, 2026

    @stackbilt-admin
    MemberAuthor

    Progress update (2026-05-06):

    Next phase for #125:

    1. Port login/architect/run/scaffold + credential/http client files into the new repo package skeleton.
    2. Stand up release workflow with npm trusted-publisher OIDC.
    3. Publish initial @stackbilt/build version and validate install + stackbilt run flow.
  3. stackbilt-admin commented on May 23, 2026

    @stackbilt-admin
    MemberAuthor

    Bootstrap PR opened: Stackbilt-dev/stackbilt-build#2. Package structure, all 4 commands, credentials, http-client, and 3 test files ported. Release workflow mirrors charter's OIDC trusted-publisher pattern. Ready for review.

  4. stackbilt-admin commented on May 23, 2026

    @stackbilt-admin
    MemberAuthor

    Phase 2 complete. @stackbilt/build@0.1.0 published to npm. OIDC Trusted Publisher configured on npmjs.com (Stackbilt-dev/build, release.yml, npm publish scope). Unblocked Phase 3 (already shipped in 0.13.0) and Phase 4 (now complete per #127).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    v1.0Targeted for Charter v1.0

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions