@opum-ai/lore 0.6.1 → 0.6.2

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.
Files changed (2) hide show
  1. package/README.md +11 -6
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -30,18 +30,23 @@ semantic exit codes, machine-readable `--json`).
30
30
 
31
31
  - Built on **Bun + TypeScript** with an exact-pinned **Commander** parser fed by
32
32
  Lore's capability manifest; Lore still owns output, errors, and process lifecycle.
33
- - Published on npm as **`@opum-ai/lore@0.6.0`** (bin `lore`) with six
33
+ - Published on npm as **`@opum-ai/lore@0.6.1`** (bin `lore`) with six
34
34
  exact-pinned platform packages, including Windows ARM64.
35
35
  - The agent bridge is a generated **`.claude/skills/lore/SKILL.md`** plus a tiny
36
36
  CLAUDE.md nudge and `lore instructions`. An **MCP server is secondary and
37
37
  deferred to v2**.
38
38
 
39
- > **Status: 0.6.0 released.** Tag `v0.6.0`, the qualified workflow artifacts,
39
+ > **Status: 0.6.1 released.** Tag `v0.6.1`, the qualified workflow artifacts,
40
40
  > all seven public `@opum-ai/lore*` npm packages, and a clean registry install
41
- > agree on `0.6.0`. Trusted Publishing is configured for every package; the
42
- > owner lifted the `publish: true` prohibition on 2026-08-29 (LCLI-278), so a
43
- > release is a single `gh workflow run release.yml --ref v<version> -f
44
- > publish=true` dispatch. See
41
+ > agree on `0.6.1`.
42
+ >
43
+ > **Releases are currently manual, not a single dispatch.** OIDC trusted
44
+ > publishing is configured on every package but cannot authenticate: GitHub
45
+ > issues immutable-format OIDC subject claims for this repository and npm
46
+ > matches the classic form, so `publish: true` fails with `E404` (LCLI-482).
47
+ > `0.6.1` was therefore published with `scripts/publish-release.sh` and, unlike
48
+ > `0.6.0`, **carries no provenance attestation** — provenance requires the CI
49
+ > OIDC path. See
45
50
  > [Lore CLI release truth](docs/reference/lore-cli-release-truth.md).
46
51
 
47
52
  ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@opum-ai/lore",
3
- "version": "0.6.1",
3
+ "version": "0.6.2",
4
4
  "author": "Opum AI",
5
5
  "repository": {
6
6
  "type": "git",
@@ -38,12 +38,12 @@
38
38
  "zod": "4.4.3"
39
39
  },
40
40
  "optionalDependencies": {
41
- "@opum-ai/lore-darwin-arm64": "0.6.1",
42
- "@opum-ai/lore-darwin-x64": "0.6.1",
43
- "@opum-ai/lore-linux-arm64": "0.6.1",
44
- "@opum-ai/lore-linux-x64": "0.6.1",
45
- "@opum-ai/lore-win32-arm64": "0.6.1",
46
- "@opum-ai/lore-win32-x64": "0.6.1"
41
+ "@opum-ai/lore-darwin-arm64": "0.6.2",
42
+ "@opum-ai/lore-darwin-x64": "0.6.2",
43
+ "@opum-ai/lore-linux-arm64": "0.6.2",
44
+ "@opum-ai/lore-linux-x64": "0.6.2",
45
+ "@opum-ai/lore-win32-arm64": "0.6.2",
46
+ "@opum-ai/lore-win32-x64": "0.6.2"
47
47
  },
48
48
  "bin": {
49
49
  "lore": "bin/lore.cjs"