release check

.github/workflows/release.yml

@@ -0,0 +1,15 @@
+on:
+  push:
+    tags:
+    - '*'
+
+name: release
+
+jobs:
+  check:
+    name: check
+    runs-on: ubuntu-22.04
+    steps:
+    - uses: actions/checkout@v3
+    - run: "npm diff --diff=@hazae41/zepar@${{github.ref_name}} --diff=."
+    - run: "[[ -z $(npm diff --diff=@hazae41/zepar@${{github.ref_name}} --diff=.) ]]"

README.md

@@ -79,4 +79,11 @@ If the output is empty then the bytecode is the same as the one I commited
 Each time I commit to the repository, the GitHub's CI does the following:
 - Clone the repository
 - Reproduce the build using `docker compose up --build`
-- Throw an error if the `git status --porcelain` output is not empty
+- Throw an error if the `git status --porcelain` output is not empty
+
+Each time I release a new version tag on GitHub, the GitHub's CI does the following:
+- Clone the repository
+- Do not reproduce the build, as it's already checked by the task above
+- Throw an error if there is a `npm diff` between the cloned repository and the same version tag on NPM
+
+If a version is present on NPM but not on GitHub, do not use!

package.json

@@ -1,7 +1,7 @@
 {
   "type": "module",
   "name": "@hazae41/zepar",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "author": "hazae41",
   "license": "Unlicense",
   "description": "WebAssembly port of RustCrypto's AES + CTR, Rust implementations of AES encryption with CTR mode.",