@oh-my-ai-sdk/omakase 0.1.3 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -705,11 +705,22 @@ exactly once.
705
705
 
706
706
  ## Automatic releases
707
707
 
708
- Merging a new package version to `main` triggers `release.yml`. The publisher
709
- requires successful CI on that exact commit, builds once, and runs the installed
710
- ordinary/durable MCP proof before publishing the tested tarball. It checks npm's
711
- integrity and repeats the proof against a registry installation. Published
712
- versions are immutable; normal pushes skip versions already on npm.
708
+ An eligible merge to `main` triggers `release.yml`. CI automatically assigns the
709
+ next **patch** on the owner-approved release line: `0.1.3` → `0.1.4` → `0.1.5`.
710
+ Do not hand-bump the patch in `package.json`. Its major/minor must match the
711
+ `OMAKASE_RELEASE_LINE` variable in GitHub's **npm-omakase** environment; changing
712
+ source to `0.2.0` alone fails closed. Only Charles may authorize changing that
713
+ setting and the source manifest to a new major/minor line.
714
+
715
+ The publisher requires successful CI on that exact commit, reserves a
716
+ package-scoped `omakase@<version>` tag, installs locked dependencies, then stamps
717
+ the artifact's version and source commit. It builds once and runs the installed
718
+ ordinary/durable MCP proof before publishing the tested tarball, checks npm's
719
+ integrity, and repeats the proof against a registry installation.
720
+ Reservations are immutable: retries reuse the same version, including after a
721
+ publish whose registry visibility was delayed. Failed builds can leave patch
722
+ gaps; do not delete or move their tags. A superseded unpublished reservation
723
+ cannot replace a newer release on `latest`.
713
724
 
714
725
  Omakase continues on the `0.1.x` release line: `0.1.1` includes the functionality
715
726
  previously published as `0.2.0-beta.3`. Durable execution remains an opt-in beta
@@ -718,17 +729,28 @@ Normal installs use `@oh-my-ai-sdk/omakase` on `latest`. Previously published
718
729
  prereleases remain available; existing pins or `@beta` installs must switch to
719
730
  `0.1.1` or `@latest` to follow this release line.
720
731
 
721
- Prereleases use their named `alpha`, `beta`, or `rc` channel; only stable versions
722
- update `latest`.
732
+ Automatic publication produces stable `0.1.x` versions on `latest`; it does not
733
+ infer minor/major bumps or prereleases from commit messages. The early-stage
734
+ patch policy includes reviewed features, not just fixes; it is not a claim that
735
+ all APIs are stable.
723
736
 
724
737
  One-time npm setup: in this package's **Settings → Trusted publishing**, authorize
725
738
  GitHub owner `archeism`, repository `oh-my-ai`, workflow **`release.yml`**, environment
726
739
  **`npm-omakase`**, with direct **`npm publish`** allowed. The GitHub environment
727
740
  permits only branch `main`, with no required reviewers or per-release approval.
728
741
  A staged-publish permission alone does not enable automatic releases. No npm token secret is used.
742
+ Set the environment variable `OMAKASE_RELEASE_LINE` to `0.1` during setup.
743
+ The publisher has tag-writing permission, not environment-administration
744
+ permission. Moving to `0.2` or `1.0` is an explicit owner decision, not a routine
745
+ release approval.
746
+ Bootstrap an existing publication with its verified `omakase@<version>` source
747
+ tag before enabling this allocator (Omakase's baseline is `omakase@0.1.3`).
748
+ New allocations must descend from the newest reservation, not necessarily equal
749
+ the current main tip: an unrelated main merge must not strand an eligible release.
729
750
  See [npm's trusted-publisher setup](https://docs.npmjs.com/trusted-publishers/).
730
751
 
731
- After fixing a publishing failure, retry from reviewed `main`:
752
+ After fixing a publishing failure, rerun the failed Actions run to resume its
753
+ exact source reservation. To release or verify the current reviewed `main`:
732
754
 
733
755
  ```sh
734
756
  gh workflow run release.yml --repo archeism/oh-my-ai --ref main
@@ -1,5 +1,5 @@
1
1
  {
2
- "generatedAt": "2026-10-12T00:27:02.038Z",
2
+ "generatedAt": "2026-10-12T07:09:16.138Z",
3
3
  "entry": "worker.mjs",
4
4
  "runtime": "bun >=1.3.14 (launched per run by the host; stdin/stdout JSON wire)",
5
5
  "adapters": {
@@ -1,8 +1,8 @@
1
1
  {
2
- "generatedAt": "2026-10-12T00:27:02.038Z",
2
+ "generatedAt": "2026-10-12T07:09:16.137Z",
3
3
  "source": "resolved package manifests walked from esbuild metafile inputs (authoritative, not pin literals)",
4
4
  "packages": {
5
- "@oh-my-ai-sdk/omakase": "0.1.3",
5
+ "@oh-my-ai-sdk/omakase": "0.1.4",
6
6
  "@ai-sdk/provider": "4.0.7",
7
7
  "eventsource-parser": "3.1.1",
8
8
  "@workflow/serde": "4.1.0",
@@ -1,5 +1,5 @@
1
1
  {
2
- "generatedAt": "2026-10-12T00:26:58.090Z",
2
+ "generatedAt": "2026-10-12T07:09:10.408Z",
3
3
  "source": "resolved package manifests from the isolated scratch graph (authoritative, not pin literals)",
4
4
  "packages": {
5
5
  "@workflow/utils": "4.1.4",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@oh-my-ai-sdk/omakase",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "type": "module",
5
5
  "description": "One Code Mode tool host for native AI SDK agents and MCP clients, with a stateful skills service",
6
6
  "exports": {
@@ -96,5 +96,6 @@
96
96
  "examples/agent-tasks.config.mjs",
97
97
  "README.md",
98
98
  "LICENSE"
99
- ]
99
+ ],
100
+ "gitHead": "6ee633e79fa90d4114f7c32a857f60d63a7c100e"
100
101
  }