tink-harness 1.2.0 → 1.2.1

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "tink",
3
3
  "description": "A small harness layer for Claude Code and Codex.",
4
- "version": "1.2.0",
4
+ "version": "1.2.1",
5
5
  "author": {
6
6
  "name": "dotori"
7
7
  }
package/CHANGELOG.md CHANGED
@@ -7,6 +7,14 @@ All notable changes to Tink are tracked here.
7
7
  No unreleased changes yet.
8
8
 
9
9
 
10
+ ## [1.2.1] - 2026-06-07
11
+
12
+ ### Changed
13
+
14
+ - README now shows a GitHub Release badge and an explicit latest release line so the repository front page reflects the current release even when badge caches lag.
15
+ - Published the README/release-display patch so GitHub source and the npm package stay aligned after the v1.2.0 publish.
16
+
17
+
10
18
  ## [1.2.0] - 2026-06-07
11
19
 
12
20
  ### Added
package/README.ko.md CHANGED
@@ -8,6 +8,8 @@ Claude Code와 Codex를 위한 작은 하네스 레이어입니다.
8
8
 
9
9
  Tink는 지금 작업에 맞는 하네스를 고르고, 실행 상태를 보이게 만들고, 실제 사용 중 생긴 실패와 피드백으로 하네스 세트를 개선합니다.
10
10
 
11
+ **최신 릴리스:** v1.2.1 — Codex 스킬 표면 정리, context 기록, portable verification, 외부 context 안전 기준.
12
+
11
13
  [English](README.md) · **한국어**
12
14
 
13
15
  ---
package/README.md CHANGED
@@ -16,14 +16,17 @@
16
16
  <em>Tink is <strong>knit</strong> in reverse: untying tangled workflows and knitting better ones back together. It also nods to Tinker Bell, the small helper at your side.</em>
17
17
  </p>
18
18
 
19
- <p>
20
- <a href="https://www.npmjs.com/package/tink-harness"><img src="https://img.shields.io/npm/v/tink-harness?label=npm&color=cb3837" alt="npm version"></a>
21
- <a href="https://github.com/dotoricode/tink-harness/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/dotoricode/tink-harness/ci.yml?branch=main&label=ci" alt="CI"></a>
22
- <a href="https://github.com/dotoricode/tink-harness/blob/main/LICENSE"><img src="https://img.shields.io/github/license/dotoricode/tink-harness" alt="License"></a>
23
- <a href="https://github.com/dotoricode/tink-harness/stargazers"><img src="https://img.shields.io/github/stars/dotoricode/tink-harness?style=social" alt="GitHub stars"></a>
24
- </p>
25
-
26
- **English** · [한국어](README.ko.md)
19
+ <p>
20
+ <a href="https://github.com/dotoricode/tink-harness/releases/tag/v1.2.1"><img src="https://img.shields.io/github/v/release/dotoricode/tink-harness?label=release&color=2ea44f" alt="GitHub release"></a>
21
+ <a href="https://www.npmjs.com/package/tink-harness"><img src="https://img.shields.io/npm/v/tink-harness?label=npm&color=cb3837" alt="npm version"></a>
22
+ <a href="https://github.com/dotoricode/tink-harness/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/dotoricode/tink-harness/ci.yml?branch=main&label=ci" alt="CI"></a>
23
+ <a href="https://github.com/dotoricode/tink-harness/blob/main/LICENSE"><img src="https://img.shields.io/github/license/dotoricode/tink-harness" alt="License"></a>
24
+ <a href="https://github.com/dotoricode/tink-harness/stargazers"><img src="https://img.shields.io/github/stars/dotoricode/tink-harness?style=social" alt="GitHub stars"></a>
25
+ </p>
26
+
27
+ <p><strong>Latest release:</strong> v1.2.1 — focused Codex skills, visible context artifacts, portable verification, and safer external context.</p>
28
+
29
+ **English** · [한국어](README.ko.md)
27
30
 
28
31
  ---
29
32
 
package/VERSIONING.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Versioning
2
2
 
3
- Current version: `1.2.0`
3
+ Current version: `1.2.1`
4
4
 
5
5
  Tink follows semver from `1.0.0` onward.
6
6
 
@@ -0,0 +1,25 @@
1
+ # PR draft: v1.2.1 README and GitHub release display
2
+
3
+ ## 문제
4
+
5
+ `tink-harness@1.2.0`을 npm에 publish한 뒤 GitHub README 상단과 GitHub Releases 카드도 최신 릴리스를 명확히 보여줘야 한다는 점을 확인했다. README 변경을 GitHub에만 두면 npm tarball과 repository source가 달라질 수 있었다.
6
+
7
+ ## 해결
8
+
9
+ - README 상단에 GitHub Release badge를 추가했다.
10
+ - README와 한국어 README에 `Latest release` / `최신 릴리스` 문구를 추가했다.
11
+ - `1.2.1` 패치 버전으로 올려 README 표시 변경까지 npm package와 GitHub source가 같은 버전으로 맞도록 했다.
12
+
13
+ ## 검증
14
+
15
+ - `npm test`
16
+ - `git diff --check`
17
+ - `npm pack --dry-run --json`
18
+ - `npm publish --dry-run`
19
+ - `npm publish`
20
+ - `npm view tink-harness version`
21
+
22
+ ## 참고
23
+
24
+ - `1.2.0`은 기능 릴리스로 유지한다.
25
+ - `1.2.1`은 GitHub README와 Release 표시를 최신 상태로 맞추기 위한 릴리즈 정합성 패치다.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tink-harness",
3
- "version": "1.2.0",
3
+ "version": "1.2.1",
4
4
  "description": "Self-growing harnesses for Claude Code and Codex.",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -11,14 +11,14 @@
11
11
  "bin/",
12
12
  "templates/",
13
13
  ".claude-plugin/",
14
- "commands/",
15
- "skills/",
16
- "hooks/",
17
- "docs/compatibility-policy.md",
18
- "docs/mcp-safe-profile.md",
19
- "docs/repo-signals.md",
20
- "docs/pr/",
21
- "README.md",
14
+ "commands/",
15
+ "skills/",
16
+ "hooks/",
17
+ "docs/compatibility-policy.md",
18
+ "docs/mcp-safe-profile.md",
19
+ "docs/repo-signals.md",
20
+ "docs/pr/",
21
+ "README.md",
22
22
  "CHANGELOG.md",
23
23
  "VERSIONING.md",
24
24
  "LICENSE"