Skip to content

[009] Configure automated changelog generation#79

Merged
xlabtg merged 4 commits intomainfrom
issue-38-5187c6635f58
Apr 25, 2026
Merged

[009] Configure automated changelog generation#79
xlabtg merged 4 commits intomainfrom
issue-38-5187c6635f58

Conversation

@konard
Copy link
Copy Markdown
Collaborator

@konard konard commented Apr 25, 2026

Summary

  • Add a changelog generator that builds reviewed release notes from merged pull requests.
  • Add npm scripts for previewing, writing, and checking changelog entries.
  • Wire changelog preview into release validation CI and document the manual review workflow.

Issue

Fixes #38

Tests

  • npm test
  • npm run validate:foundation
  • npm run validate:release
  • npm run changelog:check

Risk

  • The generator reads merged pull request metadata through GitHub CLI; maintainers still review generated notes before publication.

Screenshots or recordings

Not applicable.

Security and privacy

  • This PR does not include secrets, production credentials, access tokens, Telegram API hashes, private keys, or private message content.
  • Generated release notes include an explicit privacy review gate before publication.

Adding .gitkeep for PR creation (default mode).
This file will be removed when the task is complete.

Issue: #38
@konard konard self-assigned this Apr 25, 2026
@konard konard changed the title [WIP] [009] Configure automated changelog generation [009] Configure automated changelog generation Apr 25, 2026
@konard konard marked this pull request as ready for review April 25, 2026 05:42
@konard
Copy link
Copy Markdown
Collaborator Author

konard commented Apr 25, 2026

Solution summary

Implemented and pushed the changelog workflow for issue #38.

PR: #79

What changed:

  • Added scripts/generate-changelog.mjs and src/foundation/changelog.mjs.
  • Added CHANGELOG.md with generated, reviewed 0.1.0 notes linking merged PRs and referenced issues.
  • Added npm scripts: changelog, changelog:write, changelog:check.
  • Wired changelog preview into release validation CI with GH_TOKEN.
  • Documented the manual review workflow in docs/release-strategy.md.
  • Added automated tests for grouping, issue links, redaction, and changelog insertion.

Validation:

  • npm test passed.
  • npm run validate:foundation passed.
  • npm run validate:release passed.
  • npm run changelog:check passed.
  • GitHub CI is passing on head SHA 2ee1aee050f49c84c8d829f2804bcbdbf48c7870.
  • PR is ready for review and mergeable cleanly.

This summary was automatically extracted from the AI working session output.

@konard
Copy link
Copy Markdown
Collaborator Author

konard commented Apr 25, 2026

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

  • Model: GPT-5.5
  • Provider: OpenAI
  • Public pricing estimate: $3.704347

📊 Context and tokens usage:

  • 2.1M / 1.1M (196%) input tokens, 12.4K / 130K (10%) output tokens

Total: (120.5K + 1.9M cached) input tokens, 12.4K output tokens, $3.704347 cost

🤖 Models used:

  • Tool: OpenAI Codex
  • Requested: gpt-5.5
  • Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Gist (19654KB)


Now working session is ended, feel free to review and add any feedback on the solution draft.

@xlabtg xlabtg merged commit b13d791 into main Apr 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[009] Configure automated changelog generation

2 participants