Skip to content

feat!: merge changelog flow into root action#6

Merged
derogab merged 4 commits into
masterfrom
multi-provider-single-action
Mar 23, 2026
Merged

feat!: merge changelog flow into root action#6
derogab merged 4 commits into
masterfrom
multi-provider-single-action

Conversation

@derogab
Copy link
Copy Markdown
Member

@derogab derogab commented Mar 23, 2026

Summary

This PR replaces the split changelog actions with a single root action
so the release flow is easier to integrate and no longer depends on
passing large payloads between action entrypoints.

Changes

  • Provider support: replace the old Claude-based split flow with an
    OpenAI-compatible changelog generator that collects release data
    directly inside the action.
  • Single action design: move the main entrypoint to action.yml,
    remove the separate generate, notify, annotate, and prepare
    action entrypoints, and keep Telegram and Mixpanel behavior optional
    based on configured inputs.
  • Notifications and docs: render Telegram-safe HTML locally, keep
    Mixpanel annotations in the same action, and rewrite the README for
    the new root-level @2 usage.
  • Quality: add Python tests for the helper scripts and a GitHub
    Actions workflow that runs the test suite.

Test plan

  • python3 -m unittest discover -s tests -v
  • python3 -m py_compile scripts/openai_chat.py scripts/changelog_to_telegram_html.py tests/test_openai_chat.py tests/test_changelog_to_telegram_html.py
  • ruby -e 'require "yaml"; %w[action.yml .github/workflows/tests.yml].each { |path| YAML.load_file(path) }; puts "yaml ok"'
  • git diff --check
  • Run the tag-triggered action in a repository configured with the
    OpenAI provider settings and optional Telegram/Mixpanel secrets.

derogab added 4 commits March 23, 2026 16:21
Avoid workflow dispatch input size limits by collecting release data in
the generate action itself.

Switching to OpenAI-compatible endpoints also lets users pick their own
provider while keeping the helper scripts covered by tests and CI.
Keeping the action at the repository root makes the 2.x migration
simpler and avoids passing data between separate action entrypoints.

Telegram notifications and Mixpanel annotations remain optional so a
single integration can cover the common release workflow.
@derogab derogab changed the title feat!: replace claude with openai-compatible changelog flow feat!: merge changelog flow into root action Mar 23, 2026
@derogab derogab merged commit dde1ba1 into master Mar 23, 2026
1 check 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.

1 participant