Skip to content

pi.dev: feature installation with concrete version fails to fetch release tags from the (old) pi-mono repository #276

Description

@moormaster

Problem description
Installing pi.dev feature in a devcontainer and configuring a concrete version fails with error message
=== [ERROR] Could not find release tag for version "0.80.3" in "badlogic/pi-mono"!:

devcontainer.json

{
	// ...
	"features": {
		"ghcr.io/devcontainer-community/devcontainer-features/pi.dev:1": {
			"version": "0.80.3"
		}
	}
}

Possible causes

  1. install.sh references an old repository name badlogic/pi-mono instead of the new one earendil-works/pi

    readonly githubRepository='badlogic/pi-mono'

  2. install.sh accesses github api on the old repository badlogic/pi-mono without allowing curl to follow redirects

    curl -s "$url" | grep -Po '"tag_name": "\K.*?(?=")' | grep -E "^v?${escaped_version}$" | head -n 1

    $ curl -s https://api.github.com/repos/badlogic/pi-mono/releases
    {
      "message": "Moved Permanently",
      "url": "https://api.github.com/repositories/1035029907/releases",
      "documentation_url": "https://docs.github.com/rest/guides/best-practices-for-using-the-rest-api#follow-redirects"
    }

    adding --follow curl parameter would fix the issue, too:

    $ curl -s --follow https://api.github.com/repos/badlogic/pi-mono/releases
    [
      {
        "url": "https://api.github.com/repos/earendil-works/pi/releases/347087098",
        "assets_url": "https://api.github.com/repos/earendil-works/pi/releases/347087098/assets",
        "upload_url": "https://uploads.github.com/repos/earendil-works/pi/releases/347087098/assets{?name,label}",
        "html_url": "https://github.com/earendil-works/pi/releases/tag/v0.80.3",
        "id": 347087098,
        "author": {
          "login": "github-actions[bot]",
          "id": 41898282,
    ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions