@enormora/wall-clock 0.0.1 → 0.0.2

package/README.md

@@ -95,7 +95,7 @@ The deterministic clock implements the same `WallClock` interface and adds:
 The deterministic clock runs scheduled callbacks when time is advanced far enough.
 
 ```ts
-import { deepEqual } from 'node:assert/strict';
+import assert from 'node:assert';
 import { createDeterministicWallClock } from '@enormora/wall-clock/deterministic-wall-clock';
 
 const wallClock = createDeterministicWallClock();
@@ -110,16 +110,16 @@ wallClock.setTimeout(
 );
 
 wallClock.advanceByMilliseconds(99);
-deepEqual(calls, []);
+assert.deepStrictEqual(calls, []);
 
 wallClock.advanceByMilliseconds(1);
-deepEqual(calls, ['done']);
+assert.deepStrictEqual(calls, ['done']);
 ```
 
 Intervals run once for each elapsed interval.
 
 ```ts
-import { equal } from 'node:assert/strict';
+import assert from 'node:assert';
 import { createDeterministicWallClock } from '@enormora/wall-clock/deterministic-wall-clock';
 
 const wallClock = createDeterministicWallClock();
@@ -130,11 +130,11 @@ const intervalIdentifier = wallClock.setInterval(() => {
 }, 100);
 
 wallClock.advanceByMilliseconds(250);
-equal(count, 2);
+assert.strictEqual(count, 2);
 
 wallClock.clearInterval(intervalIdentifier);
 wallClock.advanceByMilliseconds(500);
-equal(count, 2);
+assert.strictEqual(count, 2);
 ```
 
 ## Timer behavior
@@ -230,13 +230,57 @@ just packtory-dry-run
 
 ## Publishing
 
-The package is prepared with Packtory. The dry-run command validates the package shape without publishing.
+The package is released through the manual GitHub Actions `Release` workflow. Packtory owns the release flow: it
+generates `CHANGELOG.md`, commits it to `main`, publishes to npm, pushes the package tag, and creates the GitHub Release.
+
+Pull requests that should appear in the changelog need exactly one changelog label. Supported labels:
+
+- `breaking`
+- `bug`
+- `feature`
+- `enhancement`
+- `documentation`
+- `upgrade`
+- `refactor`
+- `build`
+
+To release, go to GitHub Actions -> Release -> Run workflow.
+
+The dry-run command validates the package shape without publishing.
 
 ```sh
 just packtory-dry-run
 ```
 
-Actual publishing should use the repository release workflow once configured.
+Inspect the next release plan:
+
+```sh
+just release-plan
+```
+
+Show what would change compared to the latest published package:
+
+```sh
+just release-diff
+```
+
+Generate or update the configured changelog output:
+
+```sh
+just changelog
+```
+
+Prepare a changelog commit:
+
+```sh
+just prepare-release
+```
+
+Publish, tag, push tags, and create GitHub Releases:
+
+```sh
+just publish-release
+```
 
 ## License
 

package/package.json

@@ -22,5 +22,5 @@
     },
     "sideEffects": false,
     "type": "module",
-    "version": "0.0.1"
+    "version": "0.0.2"
 }

package/sbom.cdx.json

@@ -9,22 +9,22 @@
                 {
                     "type": "application",
                     "name": "packtory",
-                    "version": "0.0.43"
+                    "version": "0.0.46"
                 }
             ]
         },
         "component": {
             "type": "library",
             "name": "@enormora/wall-clock",
-            "version": "0.0.1",
-            "bom-ref": "pkg:npm/@enormora/wall-clock@0.0.1",
-            "purl": "pkg:npm/@enormora/wall-clock@0.0.1"
+            "version": "0.0.2",
+            "bom-ref": "pkg:npm/@enormora/wall-clock@0.0.2",
+            "purl": "pkg:npm/@enormora/wall-clock@0.0.2"
         }
     },
     "components": [],
     "dependencies": [
         {
-            "ref": "pkg:npm/@enormora/wall-clock@0.0.1"
+            "ref": "pkg:npm/@enormora/wall-clock@0.0.2"
         }
     ]
 }