claude-code-autoconfig 1.0.83 → 1.0.84

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-code-autoconfig",
3
- "version": "1.0.83",
3
+ "version": "1.0.84",
4
4
  "description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
5
5
  "author": "ADAC 1001 <info@adac1001.com>",
6
6
  "license": "MIT",
@@ -34,6 +34,7 @@
34
34
  "bin",
35
35
  ".claude",
36
36
  "!.claude/settings.local.json",
37
+ "!.claude/commands/publish.md",
37
38
  "CLAUDE.md"
38
39
  ],
39
40
  "engines": {
@@ -1,24 +0,0 @@
1
- <!-- @description Runs tests, bumps version, commits, and publishes to npm. -->
2
-
3
- # Publish
4
-
5
- Run tests, bump the patch version, commit, push, and publish to npm.
6
-
7
- ## Steps
8
-
9
- 1. Run the project's test suite (`npm test`)
10
- 2. **If tests fail, stop here.** Do not publish broken code.
11
- 3. Check for uncommitted changes. If there are any:
12
- a. Stage all changes (`git add -A`)
13
- b. Generate a conventional commit message based on the diff
14
- c. Commit the changes
15
- 4. Bump the version: `npm version patch`
16
- 5. Push the commit and tag: `git push && git push --tags`
17
- 6. Publish to npm: `npm publish`
18
- 7. Output the new version number on success
19
-
20
- ## Important
21
-
22
- - Always run tests before publishing — never skip this step
23
- - If any step fails, stop immediately and report the error
24
- - Do not use `--force` on publish unless the user explicitly asks