czlonkowski
b2300429fd
fix: resolve release workflow YAML parsing errors with script-based approach
Replace heredoc-in-command-substitution pattern with script-based release notes
generation to fix YAML parser interpretation issues.
Root cause:
- GitHub Actions YAML parser interprets heredoc content inside $() as YAML structure
- Line 149 error: parser expected ':' after '### Initial Release'
- Pattern: NOTES=$(cat <<EOF...) causes content to be parsed as YAML
Solution:
- Created scripts/generate-initial-release-notes.js (mirrors generate-release-notes.js)
- Script outputs markdown that YAML parser doesn't interpret
- Keeps --- separators (safe in script output, not in heredocs)
- Consistent pattern across workflow (all release notes from scripts)
Benefits:
- Fixes CI failures since Oct 24 (commit 0e26ea6)
- YAML validates successfully with Python yaml.safe_load()
- Easier to test and maintain release note generation
- No need to change --- to ___ separators
Testing:
- Script generates correct markdown locally
- YAML syntax validated
- TypeScript builds and type checks pass
Fixes: Release workflow runs 18806809439, 18806655633, 18806137471, etc.
Related: PR #371 (different approach attempted)
Concieved by Romuald Członkowski - www.aiadvisors.pl/en
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-25 21:00:17 +02:00
..
2025-06-14 10:36:54 +02:00
2025-10-11 18:16:56 +02:00
2025-06-25 10:55:34 +02:00
2025-07-28 22:56:15 +02:00
2025-06-14 10:36:54 +02:00
2025-06-13 11:54:42 +02:00
2025-06-08 08:21:38 +00:00
2025-10-04 09:30:43 +02:00
2025-08-02 21:14:00 +02:00
2025-06-09 00:33:17 +02:00
2025-06-09 00:33:17 +02:00
2025-06-09 00:33:17 +02:00
2025-07-28 22:45:09 +02:00
2025-07-28 23:25:42 +02:00
2025-07-28 22:56:15 +02:00
2025-10-25 21:00:17 +02:00
2025-10-24 11:24:00 +02:00
2025-07-28 22:56:15 +02:00
2025-07-15 16:46:30 +02:00
2025-06-15 01:11:02 +02:00
2025-07-11 00:48:43 +02:00
2025-07-17 21:35:00 +02:00
2025-06-08 08:21:38 +00:00
2025-06-08 08:21:38 +00:00
2025-07-10 12:49:25 +02:00
2025-08-02 21:14:00 +02:00
2025-09-14 11:03:47 +02:00
2025-10-12 00:09:55 +02:00
2025-06-16 12:37:45 +02:00
2025-07-28 23:25:42 +02:00
2025-08-02 00:01:01 +02:00
2025-10-06 23:36:56 +02:00
2025-07-10 09:22:34 +02:00
2025-09-03 14:12:01 -07:00
2025-07-31 11:48:31 +02:00
2025-10-07 10:53:28 +02:00
2025-06-18 23:09:18 +02:00
2025-06-13 16:12:40 +02:00
2025-06-26 14:30:45 +02:00
2025-10-04 11:06:14 +02:00
2025-09-22 21:05:27 +02:00
2025-09-22 21:05:27 +02:00
2025-06-29 17:43:29 +02:00
2025-07-10 09:22:34 +02:00
2025-09-22 23:16:24 +02:00
2025-07-11 00:48:43 +02:00
2025-07-11 00:48:43 +02:00
2025-07-11 00:48:43 +02:00
2025-07-10 09:22:34 +02:00
2025-07-11 00:48:43 +02:00
2025-06-13 13:10:20 +02:00
2025-07-10 09:22:34 +02:00
2025-09-20 01:13:02 +02:00
2025-09-20 01:13:02 +02:00
2025-08-01 14:23:48 +02:00
2025-06-29 17:43:29 +02:00
2025-06-26 14:30:45 +02:00
2025-06-26 14:30:45 +02:00
2025-09-24 23:57:25 +02:00
2025-06-14 10:36:54 +02:00
2025-08-02 21:14:00 +02:00
2025-07-11 00:48:43 +02:00
2025-07-15 16:46:30 +02:00
2025-06-14 15:02:49 +02:00
2025-07-06 17:01:05 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-10-03 15:53:13 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-06-26 12:25:06 +02:00
2025-07-15 16:46:30 +02:00
2025-10-07 07:59:00 +02:00
2025-07-10 09:22:34 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-09-26 09:06:19 +02:00
2025-10-24 09:59:17 +02:00
2025-08-02 00:01:01 +02:00
2025-06-16 00:03:20 +02:00
2025-08-02 00:01:01 +02:00
2025-07-28 23:25:42 +02:00
2025-07-28 23:25:42 +02:00