Skip to content

Owner steps: what is left after the code work #56

Open

Description

@blockmandev

Everything below needs the owner (an account, a real editor, an admin terminal, or a decision). The code for each is done and merged.

Try for real

Decide

After the first release (#18)

Publish (last)

Still tracked in their own issues: #18 (release), #19 (codex login), #22 (hands-on checks), #38 and #40 (sbx on Windows).

Activity

  1. blockmandev commented on Nov 13, 2026

    @blockmandev
    MemberAuthor

    Copy-paste steps for each item (prepared 2026-11-13)

    Never paste a token into a chat. Type it only into the command or website that asks for it, or store it with gh secret set NAME.

    0. First: a new release (needs your OK)

    The only release, v0.1.0, still ships sbx and none of the work merged on 2026-11-13: insbx, the fast sandbox, the security fixes, codex. Publishing anything before a new release would hand people the old build.

    • You: say "release v0.2.0".
    • I then: bump the version (the release workflow refuses a tag that doesn't match Cargo.toml), merge, and push the tag v0.2.0. The release workflow builds the archives, and package-check makes the winget/Scoop/Homebrew files as the package-manifests artifact.

    1. Package managers (after the release)

    Fetch the generated files:

    gh run list --workflow package-check.yml --limit 1        # note the run id
    gh run download <RUN_ID> -n package-manifests -D manifests
    • Scoop (your own bucket):
      gh repo create incordai/scoop-bucket --public --clone
      mkdir scoop-bucket/bucket && cp manifests/scoop/incode.json scoop-bucket/bucket/
      cd scoop-bucket && git add . && git commit -m "incode 0.2.0" && git push
      Users: scoop bucket add incord https://github.com/incordai/scoop-bucket then scoop install incode.
    • Homebrew (your own tap):
      gh repo create incordai/homebrew-tap --public --clone
      mkdir homebrew-tap/Formula && cp manifests/homebrew/incode.rb homebrew-tap/Formula/
      cd homebrew-tap && git add . && git commit -m "incode 0.2.0" && git push
      Users: brew install incordai/tap/incode.
    • winget (Microsoft reviews it, takes a few days):
      winget install wingetcreate
      wingetcreate submit --token <A GITHUB TOKEN WITH public_repo> manifests\winget

    I can do the Scoop and Homebrew ones for you: gh here is signed in as you. They create two public repos under incordai, so I'll only do it when you say so.

    2. SDKs

    • Python (PyPI, package incode_sdk): make an account at https://pypi.org (it requires 2FA), then Account settings > API tokens > "Add API token". Then:
      cd sdk/python
      python -m pip install --upgrade build twine
      python -m build
      python -m twine upload dist/*     # user: __token__  password: the token
    • TypeScript (npm, @incord/incode-sdk): make an account at https://www.npmjs.com, then create the free organisation incord (Add Organization > free plan, public packages). Then:
      cd sdk/typescript
      npm ci && npm run build
      npm login
      npm publish --access public

    3. VS Code extension (publisher incordai, already in package.json)

    • Marketplace: sign in at https://marketplace.visualstudio.com/manage with a Microsoft account and create the publisher incordai. Then create an Azure DevOps personal access token with scope Marketplace > Manage at https://dev.azure.com, and run:
      cd editors/vscode && npm ci
      npx @vscode/vsce publish -p <THE TOKEN>
    • Open VSX (VSCodium, Cursor and similar): sign in at https://open-vsx.org with GitHub and create an access token. Then:
      npx ovsx create-namespace incordai -p <TOKEN>
      npx ovsx publish -p <TOKEN>
    • Publishing on every tag automatically: store the two tokens with gh secret set VSCE_PAT and gh secret set OVSX_PAT, then tell me, and I'll add the CI job.

    4. Try for real (about 15 minutes)

    • VS Code: the extension is installed. Open the incode view and try chat, Open Session, a pasted picture, and Send Selection on some code. Write down anything that looks wrong.
    • Zed / JetBrains: use the "Editors over ACP" snippets in the README. Paste one into the editor's agent settings and send one message.
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions