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: CLAUDE.md
+30-2Lines changed: 30 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
4
4
5
5
## Overview
6
6
7
-
This repo packages Capstone 6.0.0-Alpha6 as a Python package named `capstone6pwndbg` (renamed from the upstream `capstone` to avoid conflicts), intended for use by the [pwndbg](https://github.com/pwndbg/pwndbg) debugger.
7
+
This repo packages Capstone 6.0.0-Alpha7 as a Python package named `capstone6pwndbg` (renamed from the upstream `capstone` to avoid conflicts), intended for use by the [pwndbg](https://github.com/pwndbg/pwndbg) debugger.
8
8
9
9
The actual Capstone source lives in the `capstone/` git submodule — do not modify it directly. The only root-level files that matter here are:
10
10
-`python-rename.patch` — renames the Python package from `capstone` to `capstone6pwndbg` in the submodule's `setup.py`
@@ -29,4 +29,32 @@ This repo has no source code of its own. Its only purpose is:
29
29
2. Apply `python-rename.patch` to rename the published package.
30
30
3. Drive CI to build and publish wheels to PyPI.
31
31
32
-
When updating the pinned Capstone version: update the submodule ref, verify the patch still applies cleanly, then push a new `v*` tag to trigger the release workflow.
32
+
## Bumping the Capstone version
33
+
34
+
1. Fetch new tags in the submodule and check out the new tag:
35
+
```bash
36
+
cd capstone
37
+
git fetch --tags
38
+
git checkout <new-tag># e.g. 6.0.0-Alpha8
39
+
cd ..
40
+
```
41
+
42
+
2. Verify the patch still applies cleanly:
43
+
```bash
44
+
git apply --check python-rename.patch
45
+
```
46
+
If it fails, update `python-rename.patch` accordingly (regenerate the affected hunks with `git diff`).
47
+
48
+
3. Stage and commit the changes in the root repo:
49
+
```bash
50
+
git add capstone python-rename.patch
51
+
git commit -m "Bump capstone to <new-tag>"
52
+
```
53
+
54
+
4. Update the version string in `CLAUDE.md` (Overview section).
55
+
56
+
5. Push a `v*` tag to trigger CI and publish to PyPI:
0 commit comments