[FEATURE] Add release notes GitHub Actions workflow

[jjcfrancisco]

Description

GitHub Actions workflow in this repo, triggered via repository_dispatch from the monthly release DAG. Implements the behavioural spec from OvertureMaps/omf-devex#27 in a headless form: runs on the GHA runner using DuckDB+httpfs for metrics/metadata/changelog, AWS CLI for Athena, gh CLI for GitHub context, and the Anthropic API (Sonnet) for narrative sections. Opens a draft PR against this repo placing the file at blog/{NEW_DATE}-release-notes.mdx. Output format follows OvertureMaps/omf-devex#28.

Expected impact

Monthly release notes are produced automatically as a reviewable draft PR after each release DAG run, removing the manual authoring step while keeping a human in the loop for review and tweaks.

[jjcfrancisco]

John McCall (@lowlydba) this is part of the work we did at the meet up in DC. For context, we created a skill and originally spoke about doing a container application. However, I think a GHA with a repository dispatch. The intent is to trigger the action from the release_publish_dag. The only blocker I foresee is the need of an LLM's api key - Anthropic, OpenAI. Any other blockers or concerns?

[lowlydba]

The only blocker I foresee is the need of an LLM's api key - Anthropic, OpenAI. Any other blockers or concerns?

Nope! I like the shape of this better this way, too.

For the AI API key - we can utilized Bedrock (see omf-managed-environments-terraform/docs/bedrock.md#adding-a-project). We may also need to do some extending of the Tofu to allow you to use the tag systems to permission the AI project to a new/existing role for GH to assume (right now it just handles airflow, glue, etc.)

So the flow would be:

• aws-actions/configure-aws-credentials to assume a to-be-determined role
• Call the model from code
• Success! 🎉