release: prepare opencode toolkit 0.1.0-rc.1
This commit is contained in:
1 parent
6629e6ffca
commit
29d898e080
6 files changed
+34
-25
No files matched your search
@@ -4,8 +4,9 @@ A small, OpenCode V2-native package containing a curated set of engineering
|
||||
workflows adapted from ECC, plus a read-only project-status tool and a
|
||||
conservative project installer.
|
||||
|
||||
This is an early development release. It currently targets OpenCode **2.0.24**
|
||||
and Node.js **20 or newer**. It is not yet published to npm.
|
||||
This is a pre-release (`0.1.0-rc.1`) targeting OpenCode **2.0.24** and Node.js
|
||||
**20 or newer**. It is not published to npm; install the package tarball attached
|
||||
to the repository release.
|
||||
|
||||
## Included
|
||||
|
||||
@@ -19,22 +20,23 @@ and Node.js **20 or newer**. It is not yet published to npm.
|
||||
Provider/model selection remains the user's OpenCode configuration. The package
|
||||
does not enable hooks through a global install or configure credentials.
|
||||
|
||||
## Install from a local checkout
|
||||
## Install the pre-release
|
||||
|
||||
Until a release is published, install the package from its checkout in the
|
||||
project where it will be used:
|
||||
From the project where you want to use the toolkit, run:
|
||||
|
||||
```sh
|
||||
npm install --save-dev /path/to/opencode-toolkit
|
||||
npm install --save-dev "https://git.sargatxet.cloud/sargatxet/opencode-toolkit/releases/download/v0.1.0-rc.1/sargatxet-opencode-toolkit-0.1.0-rc.1.tgz"
|
||||
npx opencode-toolkit install .
|
||||
```
|
||||
|
||||
Replace `/path/to/opencode-toolkit` with the checkout path on your machine.
|
||||
This installs the prebuilt package and dependencies directly from the release;
|
||||
you do not need to clone the repository or build it. Node.js 20+ and npm must be
|
||||
installed. OpenCode itself should be version 2.0.24 for the validated setup.
|
||||
|
||||
The installer copies the selected skills and agents into `.opencode/`, registers
|
||||
the local package directory from `node_modules` in the applicable project
|
||||
config, and writes an ownership manifest. This avoids asking OpenCode to fetch
|
||||
the provisional, unpublished package name from npm. It does not overwrite
|
||||
the package from npm. It does not overwrite
|
||||
unmanaged files. If a managed file has been edited since installation, updates
|
||||
stop rather than replacing it.
|
||||
If both `opencode.json` and `.opencode/opencode.json` exist, installation stops
|
||||
@@ -67,12 +69,12 @@ For a release candidate, build the package and create a tarball from the checkou
|
||||
npm pack
|
||||
```
|
||||
|
||||
This creates `sargatxet-opencode-toolkit-0.1.0.tgz` for the current provisional
|
||||
package identity and version. In a disposable project, install that tarball
|
||||
This creates `sargatxet-opencode-toolkit-0.1.0-rc.1.tgz` for the current
|
||||
pre-release. In a disposable project, install that tarball
|
||||
rather than linking the checkout:
|
||||
|
||||
```sh
|
||||
npm install --save-dev /path/to/sargatxet-opencode-toolkit-0.1.0.tgz
|
||||
npm install --save-dev /path/to/sargatxet-opencode-toolkit-0.1.0-rc.1.tgz
|
||||
npx opencode-toolkit install .
|
||||
npx opencode-toolkit install .
|
||||
```
|
||||
|
||||
Reference in new issue
Block a user