Skip to content

Release prep: adopt v1 CI workflows, changelog, 0.1.0#1

Merged
mobileoverlord merged 6 commits into
mainfrom
jschneck/ci
Jun 24, 2026
Merged

Release prep: adopt v1 CI workflows, changelog, 0.1.0#1
mobileoverlord merged 6 commits into
mainfrom
jschneck/ci

Conversation

@mobileoverlord

Copy link
Copy Markdown
Contributor

Adopts the avocado-linux/actions@v1 reusable workflows (test on PR, release on tag), adds CHANGELOG.md, version 0.1.0. Target: qemux86-64 @ 2026/edge.

Calls avocado-linux/actions/.github/workflows/extension.yml@v1: install + ext
build against the 2024 SDK on PRs; package + keyless publish to connect on tags.
Build target auto-derived from avocado.yaml.
- test.yml: PR build check (target qemux86-64 @ 2026/edge)
- release.yml: tag/dispatch package + publish (PAT auth)
- CHANGELOG.md: 0.1.0 initial release
Add a 2024/edge-next matrix row alongside 2026/edge so this extension also
publishes into the 2024 pre-release test channel (edge-next), leaving 2024/edge
served from its previous build. Renderers + the 854 bucket policy now permit
writes to 2024/edge-next/*.
Point the test workflow's matrix at 2024/edge-next (was 2026/edge) so PRs validate
each extension against the 2024 pre-release channel we now build/render. release.yml
still publishes to both 2026/edge and 2024/edge-next.
Use docker.io/avocadolinux/sdk:{{ env.AVOCADO_DISTRO_RELEASE }} (drop the
-{{ env.AVOCADO_DISTRO_CHANNEL }} suffix). The SDK container is published per
release, not per channel, so a channel like edge-next has no matching image tag;
the release tag resolves for any channel (incl. edge-next test legs).
@mobileoverlord mobileoverlord merged commit 49c8b79 into main Jun 24, 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