[cfg] v0.5.1-pre25 release json#528
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the project’s published release metadata and the release-updater script to handle both current and legacy GitHub release asset naming schemes, ensuring downstream consumers can reliably locate the correct binaries/images across tags.
Changes:
- Refactors release asset filename matching in
scripts/update-release-json.pyto support multiple binary naming variants (includingmacvsdarwin, optional embedded versions, and_versionsuffixes). - Expands
scripts/test_update_packaging.pycoverage to validate the new regex patterns and release-selection behaviour for v0.5.0 stable assets. - Refreshes published release metadata in
public_html/src/_data/release.jsonand Raspberry Pi Imager feed data inimage/os-list-velocity.jsonto v0.5.0 stable and v0.5.1-pre25 prerelease.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
scripts/update-release-json.py |
Adds a helper to build more flexible binary asset regexes and updates platform patterns accordingly. |
scripts/test_update_packaging.py |
Adds tests to confirm the new asset patterns and stable release selection with v0.5.0 naming variants. |
public_html/src/_data/release.json |
Updates stable/prerelease versions, URLs, and hashes to current release assets. |
image/os-list-velocity.json |
Updates the Raspberry Pi Imager entry to point at the new prerelease image and metadata. |
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.
Purpose
This pull request updates the release metadata and asset handling to support new and legacy binary naming conventions for the
velocity.reportproject, ensuring compatibility with both current and previous release asset names. It also updates the release data to the latest versions and adds comprehensive tests for the new asset name patterns.Changes
Release asset naming and pattern handling:
scripts/update-release-json.pyto support both new (velocity-report-linux-arm64_0.5.0,velocity-report-mac-arm64_0.5.0) and legacy (velocity-report-linux-arm64,velocity-report-mac-arm64) binary naming schemes, using a new helper functionbuild_binary_asset_patternand updated regex patterns.scripts/test_update_packaging.pyto ensure the new asset patterns match all expected binary names and that release picking logic correctly handles both naming variants.Release metadata updates:
public_html/src/_data/release.jsonto reference the latest stable (0.5.0) and prerelease (0.5.1-pre25) versions, including new URLs, SHA256 hashes, and asset names for Linux ARM64, Mac ARM64, and Raspberry Pi image assets. [1] [2] [3]velocity.reportentry inimage/os-list-velocity.jsonto point to the new prerelease image (0.5.1-pre25), with updated download URL, sizes, hashes, and release date.Checklist
DESIGN.md.README.mdis up to date.docs/DEVLOG.mdis up to date.