feat!: merge changelog flow into root action#6
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
OpenAI-compatible changelog generator that collects release data
directly inside the action.
action.yml,remove the separate
generate,notify,annotate, andprepareaction entrypoints, and keep Telegram and Mixpanel behavior optional
based on configured inputs.
Mixpanel annotations in the same action, and rewrite the README for
the new root-level
@2usage.Actions workflow that runs the test suite.
Test plan
python3 -m unittest discover -s tests -vpython3 -m py_compile scripts/openai_chat.py scripts/changelog_to_telegram_html.py tests/test_openai_chat.py tests/test_changelog_to_telegram_html.pyruby -e 'require "yaml"; %w[action.yml .github/workflows/tests.yml].each { |path| YAML.load_file(path) }; puts "yaml ok"'git diff --checkOpenAI provider settings and optional Telegram/Mixpanel secrets.