@ggdna/dna-gg 1.1.0 → 1.1.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.
@@ -5,7 +5,7 @@
5
5
  "name": "base",
6
6
  "package": "helix",
7
7
  "ecosystem": null,
8
- "resolvedVersion": "1.13.0",
8
+ "resolvedVersion": "1.14.0",
9
9
  "via": null,
10
10
  "hash": "0x6883da335b415f9d"
11
11
  },
@@ -39,16 +39,20 @@
39
39
  "ecosystem": null,
40
40
  "resolvedVersion": null,
41
41
  "via": null,
42
- "hash": "0x8654064a14538e39"
42
+ "hash": "0xa4329d4ad27ccd8a"
43
43
  }
44
44
  ],
45
45
  "claude": {
46
46
  "claudeMdInclude": null,
47
47
  "claudeMdFromDna": true
48
48
  },
49
- "baseVersion": "1.13.0",
49
+ "baseVersion": "1.14.0",
50
50
  "baseHash": "0x6883da335b415f9d",
51
51
  "instances": [
52
+ {
53
+ "path": ".claude/CLAUDE_dna_gg.md",
54
+ "hash": "0xa02925c2acb04f6c"
55
+ },
52
56
  {
53
57
  "path": ".claude/hooks/pm-prompts.json",
54
58
  "hash": "0x988e344de6ee6200"
@@ -79,7 +83,7 @@
79
83
  },
80
84
  {
81
85
  "path": ".claude/skills/gg-review/SKILL.md",
82
- "hash": "0x9f7bbbe511238684"
86
+ "hash": "0x8583deb0630bba47"
83
87
  },
84
88
  {
85
89
  "path": ".claude/skills/gg-ticket/SKILL.md",
@@ -22,10 +22,13 @@ follow-up ticket. Section "Keep every repo in its scope" of
22
22
 
23
23
  ## 2. Document the change in every repo
24
24
 
25
- Look for `doc/guides/blog-guide.md` in every repo of the ticket, the
26
- project management repo included. It comes from the `dna_blog` layer.
25
+ Look for `doc/guides/blog-guide.md` in the project management repo and in
26
+ every other repo the ticket changed. It comes from the `dna_blog` layer.
27
27
 
28
28
  - Run `/blog` in each repo that has it; skip the others
29
+ - Skip a code repo the ticket only passes through — one nobody changed,
30
+ whatever gg committed there. gg does not release it, and a blog post
31
+ alone would force a release without a change
29
32
  - A dependency's post describes its own change only: it never names the
30
33
  repos of the ticket that use it, nor their goal — section "Describe
31
34
  every repo in its own terms" of `doc/guides/for-ai/ai-dev-guide.md`
@@ -61,4 +64,6 @@ describes.
61
64
  ## Important
62
65
 
63
66
  - Never write a blog post in a repo without `doc/guides/blog-guide.md`.
67
+ - Never write a blog post in a repo the ticket did not change, apart from
68
+ the project management repo.
64
69
  - Never start `gg do review` without the user's confirmation.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ggdna/dna-gg",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
5
5
  "keywords": [
6
6
  "dna",
@@ -33,7 +33,7 @@
33
33
  "@ggdna/dna-install": "^0.2.0"
34
34
  },
35
35
  "devDependencies": {
36
- "@types/node": "^26.6.5",
36
+ "@types/node": "^26.6.6",
37
37
  "prettier": "^3.9.10"
38
38
  },
39
39
  "scripts": {