@ggdna/dna-gg 1.5.1 → 1.6.1

package/dna/_generated.json

@@ -39,7 +39,7 @@
       "ecosystem": null,
       "resolvedVersion": null,
       "via": null,
-      "hash": "0x47e288578bf3e862"
+      "hash": "0x1be177dde62ec3b7"
     }
   ],
   "claude": {
@@ -67,7 +67,7 @@
     },
     {
       "path": ".claude/skills/gg-cleanup/SKILL.md",
-      "hash": "0x4a6903a51168486a"
+      "hash": "0x634921912309c933"
     },
     {
       "path": ".claude/skills/gg-commit/SKILL.md",
@@ -75,11 +75,11 @@
     },
     {
       "path": ".claude/skills/gg-publish/SKILL.md",
-      "hash": "0x806b4c1fd5f6f654"
+      "hash": "0x7ea44a57ed7d2ae8"
     },
     {
       "path": ".claude/skills/gg-push/SKILL.md",
-      "hash": "0x140e1b8d6cbe222e"
+      "hash": "0xe9bf8d2d00371cf3"
     },
     {
       "path": ".claude/skills/gg-review/SKILL.md",
@@ -111,11 +111,11 @@
     },
     {
       "path": "doc/guides/develop-without-ai-guide.md",
-      "hash": "0xc0d6546a678cb8cc"
+      "hash": "0x88551202636c10c0"
     },
     {
       "path": "doc/guides/for-ai/ai-dev-guide.md",
-      "hash": "0x3f2e79da5752c5fe"
+      "hash": "0xb3354db9fff082e9"
     },
     {
       "path": "doc/guides/index-guide.md",

package/dna/doc/guides/develop-without-ai-guide.md

@@ -61,6 +61,12 @@ gg do review
 
 ## Publish
 
+Publish from the workspace root and name the ticket with `-i`:
+
 ```bash
-gg do publish
+cd ~/dev/
+gg do publish -i <ticket>
 ```
+
+At the end gg moves the ticket folder to the trash. On Windows this fails
+while a terminal sits in the ticket folder ("used by another process").

package/dna/doc/guides/for-ai/ai-dev-guide.md

@@ -320,6 +320,12 @@ gg one do commit
 gg do push
 ```
 
+`gg do push` merges the main branches into the feature branches, checks
+and pushes. It upgrades no dependency: new versions, major versions
+included, arrive through the nightly build (`gg do maintain --nightly`).
+Does the ticket need a newer version of a dependency right away? Raise
+its constraint as part of the change, or run `gg do push --upgrade`.
+
 ## Review
 
 Check the diff of every repo of the ticket against its scope first (see
@@ -355,11 +361,22 @@ Afterwards load the review-light skill and execute it.
   of each repo — `gg do publish` offers them as defaults
 - If the ticket was only planned, publish the project management repo only
 
-Ask the user to run the following command **manually**:
+Ask the user to run the following command **manually** from the workspace
+root, not from the ticket folder:
 
 ```bash
-gg do publish
+cd ~/dev/ # workspace root
+gg do publish -i fix_login_crash
 ```
 
+At the end gg moves the ticket folder to the trash. Windows refuses to move
+a folder a terminal sits in ("used by another process", errno 32), so the
+terminal must stay outside the ticket — `-i` names the ticket instead.
+
 gg triggers the pull request merge and publishes the changes to the
 registry. Finally the version tag is created and pushed.
+
+A publish resolves the dependencies (`dart pub get`, `<pm> install`) and
+analyzes; it upgrades nothing and does not run the tests again — they
+passed at the commit. Only the constraints on repos the same ticket
+publishes change.

package/dna/dot-claude/skills/gg-cleanup/SKILL.md

@@ -52,10 +52,13 @@ git merge --abort
 ## 3. Remove the ticket folder
 
 ```bash
-cd ~/dev/ # workspace
-rm -rf tickets/DnaJiraPrefix-145
+cd ~/dev/ # workspace root
+rm -rf fix_login_crash
 ```
 
+On Windows, no terminal and no VS Code window may sit in the ticket folder —
+otherwise the deletion fails with "used by another process".
+
 ## 4. Update the workspace
 
 Pull `main` in the repos the ticket touched, so the workspace matches the

package/dna/dot-claude/skills/gg-publish/SKILL.md

@@ -7,6 +7,8 @@ description: Prepares the release of a reviewed ticket and hands `gg do publish`
 
 `gg do publish` merges the pull requests, publishes to the registry and
 creates and pushes the version tags. It is interactive — the user runs it.
+It resolves and analyzes every repo, but upgrades nothing and does not run
+the tests again.
 
 ## 1. Check the preconditions
 
@@ -30,12 +32,18 @@ it is interactive. Check that `CHANGELOG.md` reads well.
 
 ## 3. Let the user publish
 
-Ask the user to run this **manually** from the ticket folder:
+Ask the user to run this **manually** from the workspace root, not from the
+ticket folder. Fill in the real workspace root and ticket folder:
 
 ```bash
-gg do publish
+cd ~/dev/ # workspace root
+gg do publish -i fix_login_crash
 ```
 
+At the end gg moves the ticket folder to the trash. Windows refuses to move
+a folder a terminal sits in ("used by another process", errno 32), so the
+terminal must stay outside the ticket — `-i` names the ticket instead.
+
 It asks whether the ticket and the remote feature branches may be deleted.
 If the user declines, run `/gg-cleanup` afterwards.
 

package/dna/dot-claude/skills/gg-push/SKILL.md

@@ -15,6 +15,10 @@ gg do push
 repos that still carry uncommitted work. If it reports such a repo, run
 `/gg-commit` first and push again.
 
+It upgrades no dependency — the nightly build (`gg do maintain --nightly`)
+does. Only when the ticket needs a newer version right away, push with
+`gg do push --upgrade`.
+
 ## Important
 
 - Push only when the user asked for it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ggdna/dna-gg",
-  "version": "1.5.1",
+  "version": "1.6.1",
   "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
   "keywords": [
     "dna",