Latest release (2.0.20) has no .deb assets

[iainelder]

Happy to see that this project is releasing again!

Can you publish a new release that include the .deb assets?

The latest "test release" (2.0.20) has broken my script to install the latest release of q from Github.

My installation script gets the URL of the .deb package from the latest release, download the .deb, and installs it.

https://github.com/iainelder/dotfiles/blob/89d0cd837cc628e14b45eac6eaff1c0894ff2fa6/programs/q/install.bash#L17-L20

browser_download_url=$(
  curl -Ss 'https://api.github.com/repos/harelba/q/releases/latest' |
  jq -r '.assets[] | select(.name | test("amd64.deb")) | .browser_download_url'
)

But the latest release has no .deb assets.

https://api.github.com/repos/harelba/q/releases/latest

{
  "url": "https://api.github.com/repos/harelba/q/releases/50770029",
  "assets_url": "https://api.github.com/repos/harelba/q/releases/50770029/assets",
  "upload_url": "https://uploads.github.com/repos/harelba/q/releases/50770029/assets{?name,label}",
  "html_url": "https://github.com/harelba/q/releases/tag/2.0.20",
  "id": 50770029,
  "author": {
    "login": "harelba",
    "id": 985765,
    "node_id": "MDQ6VXNlcjk4NTc2NQ==",
    "avatar_url": "https://avatars.githubusercontent.com/u/985765?v=4",
    "gravatar_id": "",
    "url": "https://api.github.com/users/harelba",
    "html_url": "https://github.com/harelba",
    "followers_url": "https://api.github.com/users/harelba/followers",
    "following_url": "https://api.github.com/users/harelba/following{/other_user}",
    "gists_url": "https://api.github.com/users/harelba/gists{/gist_id}",
    "starred_url": "https://api.github.com/users/harelba/starred{/owner}{/repo}",
    "subscriptions_url": "https://api.github.com/users/harelba/subscriptions",
    "organizations_url": "https://api.github.com/users/harelba/orgs",
    "repos_url": "https://api.github.com/users/harelba/repos",
    "events_url": "https://api.github.com/users/harelba/events{/privacy}",
    "received_events_url": "https://api.github.com/users/harelba/received_events",
    "type": "User",
    "site_admin": false
  },
  "node_id": "RE_kwDOADJ9eM4DBrBt",
  "tag_name": "2.0.20",
  "target_commitish": "master",
  "name": "just testing release flow",
  "draft": false,
  "prerelease": false,
  "created_at": "2021-10-04T20:15:50Z",
  "published_at": "2021-10-04T20:18:34Z",
  "assets": [

  ],
  "tarball_url": "https://api.github.com/repos/harelba/q/tarball/2.0.20",
  "zipball_url": "https://api.github.com/repos/harelba/q/zipball/2.0.20",
  "body": ""
}

[harelba]

Hi! I'm sorry for the confusion, I am using 2.0.20/2.1.0 just for internally testing/debugging the new packaging mechanism,

it's not a real version, I haven't changed the links in the site, and i didn't plan to create a new tag for it. Pushed it by accident, really sorry about that. I'm not sure if it would be safe to delete the extra tags, but i'll take a look at it.

I'm creating a new packaging mechanism, because the older one was using old technologies (travis and some packaging library which is no longer maintained), and doesn't work properly anymore.

When this is done (deb/rpm already done, but windows is making me a bit crazy, as always), I'll issue the real new version i'm planning to release - It will be version 3.0.0 - A completely new version with some major additions I've done.

Harel

[iainelder]

Hi Harel,

Thanks for the response.

I'm not sure if it would be safe to delete the extra tags, but i'll take a look at it.

If moving on and releasing a new version is the easiest way to avoid the problem, then I'll happily wait.

I'll just keep it in mind to use the links on the website if I have to reinstall before then.

Looking forward to the new release! :-)

I'll close this issue now as it will be fixed with the new release.

Thanks!