drawcall
v1.0.0
Published
Create and edit 3D content in Drawcall Design, and find, install, and publish reusable assets with Drawcall Market.
Readme
drawcall
Create and edit 3D content in Drawcall Design, and find, install, and publish reusable assets with Drawcall Market.
npx drawcall auth login
npx drawcall market search robot --type model
npx drawcall design project listdrawcall composes the existing Commander implementations from @drawcall/market and
@drawcall/design. It does not start their binaries as subprocesses. Authentication is provided by
@drawcall/auth, and one token is shared by both command groups.
The token is saved in the platform config directory under drawcall/config.json. Set
DRAWCALL_AUTH_TOKEN to use an ephemeral token instead.
Package versioning
semantic-release runs on main after verification. It reads existing v* tags and Conventional Commits, updates the published package version, and creates the next tag and GitHub release. Package versions are not committed back to the repository. npm trusted publishing continues to use publish-package.yml.
Squash-merge PRs using a Conventional Commit title: fix: ... produces a patch release, feat: ... a minor release, and feat!: ... or a BREAKING CHANGE: footer a major release. Every other merged change, including docs:, chore:, and plain PR titles, produces a patch release. The squash commit uses the PR title and body, so include breaking-change details in the description. Do not manually bump package versions or create release tags.
Dependency releases directly trigger publish-package.yml. The workflow resolves the latest Drawcall dependencies into its temporary checkout, verifies the CLI, and publishes it without creating a PR or pushing to main. The largest dependency bump determines the release type together with any source changes. The published CLI manifest is the baseline, so duplicate notifications do not produce duplicate releases. Source releases also resolve current dependencies to avoid restoring older pins from main.
main accepts changes only through PRs, including automation and administrators. Required CI checks run before merge; no review approval is required. Release workflows queue rather than cancel pending runs.
