@sacho/sacho 0.3.0-dev.27 → 0.3.0-dev.28
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/package.json +7 -7
- package/skills/sacho/SKILL.md +11 -4
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sacho/sacho",
|
|
3
|
-
"version": "0.3.0-dev.
|
|
3
|
+
"version": "0.3.0-dev.28+1c820b2",
|
|
4
4
|
"description": "An opinionated changelog manager",
|
|
5
5
|
"license": "GPL-3.0-only",
|
|
6
6
|
"author": "Hong Minhee <hong@minhee.org>",
|
|
@@ -24,12 +24,12 @@
|
|
|
24
24
|
"node": ">=18"
|
|
25
25
|
},
|
|
26
26
|
"optionalDependencies": {
|
|
27
|
-
"@sacho/sacho-aarch64-apple-darwin": "0.3.0-dev.
|
|
28
|
-
"@sacho/sacho-aarch64-pc-windows-msvc": "0.3.0-dev.
|
|
29
|
-
"@sacho/sacho-aarch64-unknown-linux-musl": "0.3.0-dev.
|
|
30
|
-
"@sacho/sacho-x86_64-apple-darwin": "0.3.0-dev.
|
|
31
|
-
"@sacho/sacho-x86_64-pc-windows-msvc": "0.3.0-dev.
|
|
32
|
-
"@sacho/sacho-x86_64-unknown-linux-musl": "0.3.0-dev.
|
|
27
|
+
"@sacho/sacho-aarch64-apple-darwin": "0.3.0-dev.28+1c820b2",
|
|
28
|
+
"@sacho/sacho-aarch64-pc-windows-msvc": "0.3.0-dev.28+1c820b2",
|
|
29
|
+
"@sacho/sacho-aarch64-unknown-linux-musl": "0.3.0-dev.28+1c820b2",
|
|
30
|
+
"@sacho/sacho-x86_64-apple-darwin": "0.3.0-dev.28+1c820b2",
|
|
31
|
+
"@sacho/sacho-x86_64-pc-windows-msvc": "0.3.0-dev.28+1c820b2",
|
|
32
|
+
"@sacho/sacho-x86_64-unknown-linux-musl": "0.3.0-dev.28+1c820b2"
|
|
33
33
|
},
|
|
34
34
|
"publishConfig": {
|
|
35
35
|
"access": "public",
|
package/skills/sacho/SKILL.md
CHANGED
|
@@ -59,12 +59,16 @@ before you depend on a specific flag or output format.
|
|
|
59
59
|
- `https://sacho.dev/guide/ci-and-hooks.md` for coverage enforcement.
|
|
60
60
|
- `https://sacho.dev/guide/version-control.md` for merge drivers and
|
|
61
61
|
presets.
|
|
62
|
+
- `https://sacho.dev/guide/package-monorepos.md` for deriving sections
|
|
63
|
+
from regular package layouts.
|
|
62
64
|
- `https://sacho.dev/concepts/fragments.md`,
|
|
63
65
|
`https://sacho.dev/concepts/changelog-lifecycle.md`, and
|
|
64
66
|
`https://sacho.dev/concepts/sections.md` for the model.
|
|
65
67
|
- `https://sacho.dev/reference/commands.md` and
|
|
66
68
|
`https://sacho.dev/reference/configuration.md` for exhaustive
|
|
67
69
|
references.
|
|
70
|
+
- `https://sacho.dev/reference/section-patterns.md` for the capture
|
|
71
|
+
grammar and precedence rules.
|
|
68
72
|
- `https://sacho.dev/troubleshooting.md` when something misbehaves.
|
|
69
73
|
|
|
70
74
|
|
|
@@ -91,8 +95,10 @@ Run `sacho init` from the repository root. It creates `sacho.toml`,
|
|
|
91
95
|
drivers. Interactive setup infers issue-link templates from the remote and can
|
|
92
96
|
install commit hooks. When an existing changelog is present, it also offers
|
|
93
97
|
level-three headings found across the changelog as section candidates and
|
|
94
|
-
suggests directories and source path globs.
|
|
95
|
-
|
|
98
|
+
suggests directories and source path globs. When multiple selected headings
|
|
99
|
+
map to one unambiguous sibling package directory, it can store them as one
|
|
100
|
+
section pattern. `sacho init --interactive` forces the questions and
|
|
101
|
+
`--no-interactive` suppresses them.
|
|
96
102
|
|
|
97
103
|
Leave old released sections exactly as they are. If the current `Unreleased` or
|
|
98
104
|
`Version X` region contains entries, run `sacho import-unreleased` before
|
|
@@ -104,8 +110,9 @@ skip the import and set the version with `sacho next 1.2.0`.
|
|
|
104
110
|
|
|
105
111
|
Two configuration decisions matter early, both covered in
|
|
106
112
|
`reference/configuration.md`: whether to enforce fragment coverage
|
|
107
|
-
(`[check].paths`), and, for a monorepo, whether to define
|
|
108
|
-
|
|
113
|
+
(`[check].paths`), and, for a monorepo, whether to define explicit
|
|
114
|
+
`[[sections]]` or one `[[section-patterns]]` family so each package's changes
|
|
115
|
+
require a fragment in that package's section.
|
|
109
116
|
|
|
110
117
|
|
|
111
118
|
Writing a fragment for a change
|