Skip to content

Commit

Permalink
Merge pull request #389 from balena-os/release-tags-comment
Browse files Browse the repository at this point in the history
Upgrade-2.x.sh: Comment why we still need to use the release_tags
  • Loading branch information
flowzone-app[bot] authored Mar 28, 2024
2 parents bd8adbb + 15f4bc6 commit 952e82d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions upgrade-2.x.sh
Original file line number Diff line number Diff line change
Expand Up @@ -929,9 +929,9 @@ function get_image_location() {
if echo "${image}" | jq -e '. | length == 1' > /dev/null; then
echo "${image}" | jq -r '.[0]'
else
# TODO: Remove this release_tag fallback once the API migrates all hostApp release versions to the `release.semver` field.
# See: https://github.com/balena-io/balena-api/pull/4821
# Try with version and variant labels for backwards compatibility
# We still need to try finding the hostApp release by filtering using the deprecated release_tags,
# since the versioning format of balenaOS [2019.10.0.dev, 2022.01.0] was non-semver compliant
# and they were not migrated to the release semver fields.
image=$(CURL_CA_BUNDLE="${TMPCRT}" ${CURL} \
-H "Content-Type: application/json" \
-H "Authorization: Bearer ${APIKEY}" \
Expand Down

0 comments on commit 952e82d

Please sign in to comment.