Tracking PR for v0.2.0 release

.dockerignore

@@ -0,0 +1,38 @@
+# Include any files or directories that you don't want to be copied to your
+# container here (e.g., local build artifacts, temporary files, etc.).
+#
+# For more help, visit the .dockerignore file reference guide at
+# https://docs.docker.com/go/build-context-dockerignore/
+
+**/.DS_Store
+**/.classpath
+**/.dockerignore
+**/.env
+**/.git
+**/.gitignore
+**/.project
+**/.settings
+**/.toolstarget
+**/.vs
+**/.vscode
+**/*.*proj.user
+**/*.dbmdl
+**/*.jfm
+**/charts
+**/docker-compose*
+**/compose*
+**/Dockerfile*
+**/node_modules
+**/npm-debug.log
+**/secrets.dev.yaml
+**/values.dev.yaml
+./bin
+./target
+/bin
+/target
+LICENSE
+README.md
+accounts
+genesis.dat
+miden-store.*
+store.*

.github/ISSUE_TEMPLATE/1-bugreport.yml

@@ -12,38 +12,38 @@ body:
     attributes:
       label: "Version"
       description: "Which node version are you running?"
-      placeholder: "v0.1.0"
+      placeholder: "v0.2.0"
     validations:
       required: true
   - type: textarea
     id: other-version
     attributes:
       label: "Other packages versions"
       description: "Let us know of the versions of any other packages used. For example, which version of the client are you using?"
-      placeholder: "miden-client: v0.1.0"
+      placeholder: "miden-client: v0.2.0"
     validations:
       required: false
   - type: textarea
     id: what-happened
     attributes:
       label: "What happened?"
-      description: "Describe the behaviour you are experiencing."
+      description: "Describe the behavior you are experiencing."
       placeholder: "Tell us what you see!"
     validations:
       required: true
   - type: textarea
     id: expected-to-happen
     attributes:
       label: "What should have happened?"
-      description: "Describe the behaviour you expected to see."
+      description: "Describe the behavior you expected to see."
       placeholder: "Tell us what should have happened!"
     validations:
       required: true
   - type: textarea
     id: reproduce-steps
     attributes:
       label: "How can this be reproduced?"
-      description: "If possible, describe how to replicate the unexpected behaviour that you see."
+      description: "If possible, describe how to replicate the unexpected behavior that you see."
       placeholder: "Steps!"
     validations:
       required: true

.github/workflows/doc.yml

@@ -0,0 +1,22 @@
+# Runs documentation related jobs.
+
+name: doc
+
+on:
+  push:
+    branches: [main, next]
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+jobs:
+  doc:
+    name: doc stable on ubuntu-latest
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+      - name: Install cargo make
+        run: cargo install cargo-make
+      - name: cargo make - doc
+        run: cargo make doc

.github/workflows/lint.yml

@@ -0,0 +1,51 @@
+# Runs linting related jobs.
+
+name: lint
+
+on:
+  push:
+    branches: [main, next]
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+jobs:
+  version:
+    name: check rust version consistency
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          profile: minimal
+          override: true
+      - name: check rust versions
+        run: ./scripts/check-rust-version.sh
+
+  rustfmt:
+    name: rustfmt nightly on ubuntu-latest
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install minimal Rust with rustfmt
+        uses: dtolnay/rust-toolchain@master
+        with:
+          toolchain: nightly
+          components: rustfmt
+      - name: Install cargo make
+        run: cargo install cargo-make
+      - name: cargo make - format-check
+        run: cargo make format-check
+
+  clippy:
+    name: clippy stable on ubuntu-latest
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install minimal Rust with clippy
+        uses: dtolnay/rust-toolchain@master
+        with:
+          toolchain: stable
+          components: clippy
+      - name: Install cargo make
+        run: cargo install cargo-make
+      - name: cargo make - clippy
+        run: cargo make clippy

.github/workflows/test.yml

@@ -0,0 +1,23 @@
+# Runs testing related jobs.
+
+name: test
+
+on:
+  push:
+    branches: [main, next]
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+jobs:
+  unit-and-integration:
+    name: test stable on ubuntu-latest
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+      - name: Install cargo make
+        run: cargo install cargo-make
+      - name: cargo make - test-all
+        run: cargo make test-all

.gitignore

@@ -1,15 +1,12 @@
 # Generated by Cargo
+
 # will have compiled files and executables
 debug/
 target/
 
 # Generated by protox `file_descriptor_set.bin`
 *.bin
 
-# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries
-# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
-# Cargo.lock
-
 # These are backup files generated by rustfmt
 **/*.rs.bk
 
@@ -19,6 +16,11 @@ target/
 # VS Code
 .vscode/
 
+# JetBrains IDEs
+.idea/
+.code/
+.fleet/
+
 # Genesis files
 /accounts
 genesis.dat
@@ -28,10 +30,7 @@ genesis.dat
 *.sqlite3-shm
 *.sqlite3-wal
 
-
 # Docs ignore
-.code
-.idea
 site/
 venv/
 env/

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.2.0 (2024-04-11)
+
+* Implemented Docker-based node deployment (#257).
+* Improved build process (#267, #272, #278).
+* Implemented Nullifier tree wrapper (#275).
+* [BREAKING] Added support for public accounts (#287, #293, #294).
+* [BREAKING] Added support for public notes (#300, #310).
+* Added `GetNotesById` endpoint (#298).
+* Implemented amd64 debian packager (#312).
+
 ## 0.1.0 (2024-03-11)
 
 * Initial release.

CONTRIBUTING.md

@@ -4,10 +4,10 @@
 
 We want to make contributing to this project as easy and transparent as possible, whether it's:
 
-- Reporting a [bug](https://github.com/0xPolygonMiden/miden-node/issues/new)
+- Reporting a [bug](https://github.com/0xPolygonMiden/miden-node/issues/new?assignees=&labels=bug&projects=&template=1-bugreport.yml&title=%5BBug%5D%3A+)
 - Taking part in [discussions](https://github.com/0xPolygonMiden/miden-node/discussions)
 - Submitting a [fix](https://github.com/0xPolygonMiden/miden-node/pulls)
-- Proposing new [features](https://github.com/0xPolygonMiden/miden-node/issues/new)
+- Proposing new [features](https://github.com/0xPolygonMiden/miden-node/issues/new?assignees=&labels=enhancement&projects=&template=2-feature-request.yml&title=%5BFeature%5D%3A+)
 
  
 
@@ -80,6 +80,13 @@ For example, a new change to the `miden-node-store` crate might have the followi
 
 You can find more information about the `cargo make` commands in the [Makefile](Makefile.toml)
 
+### Testing
+After writing code different types of tests (unit, integration, end-to-end) are required to make sure that the correct behavior has been achieved and that no bugs have been introduced. You can run tests using the following command:
+
+```
+cargo make test
+```
+
 ### Versioning
 We use [semver](https://semver.org/) naming convention.