Bump ansible/ansible-content-actions/.github/workflows/changelog.yaml from 05894f1a7922836072b5a12e80f9c2ed5f489567 to 24ca2b652f231d1cdd974d96c20944354aa4bff4

[dependabot]

Bumps ansible/ansible-content-actions/.github/workflows/changelog.yaml from 05894f1a7922836072b5a12e80f9c2ed5f489567 to 24ca2b652f231d1cdd974d96c20944354aa4bff4.

Changelog

Sourced from ansible/ansible-content-actions/.github/workflows/changelog.yaml's changelog.

Using the release workflow

This GitHub action releases the collection in Ansible Automation Hub and Ansible Galaxy, it is dependent on the environment release which must contain the following secrets.

AH_TOKEN: The Automation Hub token required for to interact with Ansible Automation Hub. ANSIBLE_GALAXY_API_KEY: A Galaxy token required to interact with Ansible Galaxy.

Note - ansible-content-actions/release.yaml uses release_ah.yaml and release_galaxy.yaml internally.

Filename: release.yaml

---
name: "Release collection"
on:
  release:
    types: [published]
jobs:
release:
uses: ansible/ansible-content-actions/.github/workflows/release.yaml@main
with:
environment: release
secrets:
ah_token: ${{ secrets.AH_TOKEN }}
ansible_galaxy_api_key: ${{ secrets.ANSIBLE_GALAXY_API_KEY }}

The workflow run results in -

The release works in two parts, Automation hub release and then Ansible Galaxy release. If the Automation hub release fails, the Galaxy job is skipped.

Example showing how only Automation hub release can be made, only ah_token would be required in those cases.

Release on AH only, workflow

Filename: release_ah.yaml

---
name: "Release collection on AH"
on:
  release:
    types: [published]
jobs:
release_automation_hub:
uses: ansible/ansible-content-actions/.github/workflows/release_ah.yaml@main
</tr></table>

... (truncated)

Commits

• 24ca2b6 chore: bump python version to 3.13 from 3.12 in cml_network_integration.yaml ...
• 2f18fdf Adding reusable workflow for codecoerage for network collections (#108)
• See full diff in compare view

[djdanielsson]

LGTM