You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,9 +118,36 @@ The `repositories.json` file should be structured as follows:
118
118
poetry run rsmetacheck --input repositories.json \
119
119
--somef-output ./results/somef \
120
120
--pitfalls-output ./results/pitfalls \
121
-
--analysis-output ./results/summary.json
121
+
--analysis-output ./results/summary.json \
122
+
--notes-output ./results/notes.json
122
123
```
123
124
125
+
#### Version Discrepancy Notes
126
+
127
+
When a metadata version differs from the release version by a small margin (all version components differ by less than 2, e.g., `0.4.3.dev1` vs `0.4.2`), MetaCheck records a **note** rather than a full pitfall. To capture these observations, use the `--notes-output` flag:
128
+
129
+
```bash
130
+
poetry run rsmetacheck --input https://github.com/example/repo --notes-output ./notes.json
131
+
```
132
+
133
+
The notes file is only created when there are observations to report and the `--notes-output` path is specified. Its structure is:
134
+
135
+
```json
136
+
{
137
+
"total_notes": 1,
138
+
"notes": [
139
+
{
140
+
"repository": "example/repo",
141
+
"file_name": "repo_output.json",
142
+
"code": "P001",
143
+
"note": "Version discrepancy: metadata '0.4.3.dev1' vs release '0.4.2'"
144
+
}
145
+
]
146
+
}
147
+
```
148
+
149
+
If the version difference is significant (any component differs by 2 or more, e.g., `0.12.4` vs `0.12.1`), it is still flagged as a pitfall.
0 commit comments