diff --git a/package-lock.json b/package-lock.json
index caf40707..fc7510ae 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
     "name": "@shardlabs/starknet-hardhat-plugin",
-    "version": "0.8.0-alpha.2",
+    "version": "0.8.0-alpha.3",
     "lockfileVersion": 3,
     "requires": true,
     "packages": {
         "": {
             "name": "@shardlabs/starknet-hardhat-plugin",
-            "version": "0.8.0-alpha.2",
+            "version": "0.8.0-alpha.3",
             "license": "MIT",
             "dependencies": {
                 "@iarna/toml": "^2.2.5",
diff --git a/package.json b/package.json
index d34f1151..c50890e9 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
     "name": "@shardlabs/starknet-hardhat-plugin",
-    "version": "0.8.0-alpha.2",
+    "version": "0.8.0-alpha.3",
     "description": "Plugin for using Starknet tools within Hardhat projects",
     "main": "dist/src/index.js",
     "files": [
diff --git a/www/docs/dev.md b/www/docs/dev.md
index 0445607d..e40d13fe 100644
--- a/www/docs/dev.md
+++ b/www/docs/dev.md
@@ -162,11 +162,13 @@ $ npm version <NEW_VERSION>
 
 This will also update `package-lock.json`, create a new commit, and create a new git tag.
 
+You may want your version-bumping commit to contain the `[skip testnet]` string (documented [here](#testing-network)) to avoid testing on alpha-goerli (may postpone the version release significantly, if it will ever pass at all).
+
 If for whatever reason the publishing workflow in CI/CD cannot be executed, the version can be released manually via `scripts/npm-publish.sh`, just be sure to have an NPM access token and that you have the rights to publish.
 
 Apart from [npm](https://www.npmjs.com/package/@shardlabs/starknet-hardhat-plugin?activeTab=versions), releases are also tracked on [GitHub](https://github.com/0xSpaceShard/starknet-hardhat-plugin/releases) with [git tags](https://github.com/0xSpaceShard/starknet-hardhat-plugin/tags). Notice the prepended `v` in tag names.
 
-When the tag is pushed:
+After the npm package is released and the tag is pushed:
 
 ```bash
 $ git push origin <TAG_NAME>
@@ -178,7 +180,7 @@ Users should be notified about the usage related changes. This can be done on Te
 
 ### Docs
 
-New documentation is **automatically** deployed after publishing a new version with `scripts/npm-publish.sh`.
+New documentation is **automatically** deployed after publishing a new version with `scripts/npm-publish.sh` (also part of CI/CD).
 
 To manually deploy new documentation, run: