@link-assistant/hive-mind 0.50.8 → 0.50.10
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 +43 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,48 @@
|
|
|
1
1
|
# @link-assistant/hive-mind
|
|
2
2
|
|
|
3
|
+
## 0.50.10
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- Test patch release
|
|
8
|
+
|
|
9
|
+
## 0.50.9
|
|
10
|
+
|
|
11
|
+
### Patch Changes
|
|
12
|
+
|
|
13
|
+
- Fix stuck Docker multi-platform builds by using native ARM64 runners
|
|
14
|
+
|
|
15
|
+
The Docker publish workflow was getting stuck for hours when building ARM64 images using QEMU emulation on x86_64 runners. QEMU emulation introduces 10-100x slowdown, especially for complex Dockerfiles that compile native packages.
|
|
16
|
+
|
|
17
|
+
**Solution**: Refactored docker-publish jobs to use GitHub's native ARM64 runners (`ubuntu-24.04-arm`) with a matrix strategy:
|
|
18
|
+
- Each platform (amd64, arm64) builds natively in parallel on dedicated runners
|
|
19
|
+
- Build artifacts (digests) are uploaded and merged into a multi-platform manifest
|
|
20
|
+
- Eliminates QEMU emulation overhead entirely
|
|
21
|
+
- Build times should now be similar for both platforms (~10-15 minutes each)
|
|
22
|
+
|
|
23
|
+
This fix applies to both:
|
|
24
|
+
- `docker-publish` job (triggered by regular releases)
|
|
25
|
+
- `docker-publish-instant` job (triggered by manual instant releases)
|
|
26
|
+
|
|
27
|
+
Fixes #982
|
|
28
|
+
|
|
29
|
+
Fix Docker Publish jobs being skipped after npm publish
|
|
30
|
+
|
|
31
|
+
Added explicit shell-based output passthrough step for `published` output in both `release` and `instant-release` jobs. This ensures reliable output propagation to dependent jobs (`docker-publish` and `docker-publish-instant`).
|
|
32
|
+
|
|
33
|
+
Root cause: Node.js `appendFileSync` to `GITHUB_OUTPUT` was not reliably propagating outputs to dependent jobs. The fix uses a dedicated shell step to echo outputs, which is proven to work correctly.
|
|
34
|
+
|
|
35
|
+
Also added debug logging to `setOutput` function in `publish-to-npm.mjs` and `version-and-commit.mjs` scripts.
|
|
36
|
+
|
|
37
|
+
Add case study for harmful prompts and resource exhaustion attacks
|
|
38
|
+
|
|
39
|
+
Documents analysis of LLM resource exhaustion attacks including:
|
|
40
|
+
- Timeline and root cause analysis
|
|
41
|
+
- OWASP LLM Top 10 (2025) attack classification
|
|
42
|
+
- Attack patterns database with detection rules
|
|
43
|
+
- Five proposed solution approaches
|
|
44
|
+
- Raw attack samples for research
|
|
45
|
+
|
|
3
46
|
## 0.50.8
|
|
4
47
|
|
|
5
48
|
### Patch Changes
|