long-task-queue-reader 0.7.3-test.1 → 0.8.0-alpha.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +3 -3
- package/README.md +22 -0
- package/bun.lock +1795 -0
- package/bunfig.toml +5 -0
- package/lib/executionModes/baseExecutionMode.js +52 -0
- package/lib/executionModes/continuousExecutionMode.js +29 -0
- package/lib/executionModes/onceExecutionMode.js +25 -0
- package/lib/longTaskQueueReader.js +9 -49
- package/lib/longTaskQueueReaderBuilder.js +19 -2
- package/package.json +16 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
1
|
+
# [0.8.0-alpha.1](https://github.com/Parsimotion/long-task-queue-reader/compare/v0.7.2...v0.8.0-alpha.1) (2026-02-27)
|
|
2
2
|
|
|
3
3
|
|
|
4
|
-
###
|
|
4
|
+
### Features
|
|
5
5
|
|
|
6
|
-
*
|
|
6
|
+
* add once and continuous execution mode ([2893dea](https://github.com/Parsimotion/long-task-queue-reader/commit/2893dea67c6fbef28c257898774a6c173de0b2e9))
|
package/README.md
CHANGED
|
@@ -33,3 +33,25 @@ new LongTaskQueueBuilder()
|
|
|
33
33
|
.then (queueReader) -> queueReader.start()
|
|
34
34
|
|
|
35
35
|
```
|
|
36
|
+
## 📦 Publishing a New Version
|
|
37
|
+
|
|
38
|
+
Package publishing is now handled automatically via a GitHub Action triggered on `push` to the `main` or `master` branches.
|
|
39
|
+
|
|
40
|
+
You can also trigger it manually from the **Actions** tab using the `Release` workflow.
|
|
41
|
+
|
|
42
|
+
The workflow supports prerelease versions (e.g., `alpha`, `beta`) through the `prereleaseTag` input.
|
|
43
|
+
|
|
44
|
+
> 🔐 The release process uses the contents of the `lib/` directory generated during build.
|
|
45
|
+
|
|
46
|
+
## ✅ Commit Message Validation
|
|
47
|
+
|
|
48
|
+
[`commitlint`](https://github.com/conventional-changelog/commitlint) was added to ensure commit messages follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard.
|
|
49
|
+
|
|
50
|
+
Commit messages are automatically validated before each commit using [Husky](https://typicode.github.io/husky/).
|
|
51
|
+
|
|
52
|
+
**Example of a valid commit message:**
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
feat: add login functionality
|
|
56
|
+
```
|
|
57
|
+
> If the format is invalid, the commit will be blocked.
|