neo-decompiler 0.6.1

Minimal tooling for inspecting Neo N3 NEF bytecode
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

# Releasing neo-decompiler

1. Ensure the working tree is clean and the CI pipeline is green.
2. Update `CHANGELOG.md` with the release date and contents.
3. Bump the crate version in `Cargo.toml` and `Cargo.lock` (if present).
4. Sync the web package version with the crate version:
   ```bash
   cd web
   npm install
   npm run version:sync
   cd ..
   ```
5. If the JS package version should track the release, update `js/package.json`
   manually and run `cd js && npm test` to verify.
6. Run the full verification suite:
   ```bash
   just ci
   cd web && npm test && npm run verify:pack
   cargo package
   cargo publish --dry-run
   ```
7. Create a signed git tag: `git tag -s vX.Y.Z -m "neo-decompiler vX.Y.Z"`.
8. Push commits and tags: `git push && git push --tags`.
9. Publish to crates.io: `cargo publish`.
10. Publish the web package:
    ```bash
    cd web
    npm publish
    ```
    Prefer GitHub Actions trusted publishing. If trusted publishing is not configured on npm yet, provide an `NPM_TOKEN` secret for the `Publish Web Package` workflow instead.
11. Draft a GitHub release referencing the tag and summarising key changes, including the matching npm package version.