Skip to content

ci(imager): group imager entries into stable, other versions, development and branches - #104

Open
florian-asche wants to merge 1 commit into
mainfrom
ci/imager-json-structure
Open

florian-asche wants to merge 1 commit into
mainfrom
ci/imager-json-structure

Conversation

@florian-asche

Copy link
Copy Markdown
Owner

What does this implement/fix?

Restructures the os_list of the generated Raspberry Pi Imager JSON (scripts/generate-imager-json.py). The former single entry "all versions / branches" is split. New order:

  1. PiCompose - stable (unchanged)
  2. PiCompose - other versions: releases with a tag like v1.2.3 or 1.2.3, except the one shown as stable
  3. PiCompose - development (unchanged, the main release)
  4. PiCompose - branches: all other releases with images, for example feature/x

Empty groups are left out. Tags such as v1.2.3-rc1 count as branches.

Types of changes

  • CI / workflow change — ci

Tested on

  • Hardware / image: none. Ran the script with mocked release data (versions, main, a branch, rpi-imager-json) and checked the group order and contents. Not tested against the real GitHub API or in Raspberry Pi Imager.
  • Result: groups as described above.

Checklist

  • Shell scripts pass bash -n and workflow files are valid YAML.
  • README.md and docs/ match the change.
  • Breaking changes are described in breaking_changes.md.
  • I reviewed and understand every change in this PR (see AI policy).

🤖 Generated with Claude Code

…ment and branches

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant