Issue Tracking for every released version


Is there a way to see all issues filed for a specific release? I’d like to be able to check open issues of a release before updating to it.


1 Like

Currently no. I think this is a very good idea but GitHub cannot force users to report the version number.

1 Like

Alright… Is a change log summary published for every release version?


A changelog would be awesome.

If it’s not already there, can we create and maintain one ?


Change version number accordingly

1 Like

Thanks! Of all places, I completely forgot to check the downloads.

It might be worth noting that you can also stay on rolling release however run your own series of custom tests with each update. Then revert the update if there is an issue, disable autoupdate, and put the release notes on your desktop, trigger a script to start your car :stuck_out_tongue_winking_eye:, etc.

1 Like

Latest one :wink:

It would be great if we could have date of the release something like this:

Release notes for the update from 33340 to 33350 (2020-06-11T08:48:22+00:00)

There is the date

thx, it’s interesting that swupd info points to 404 url or it’s template url?

Distribution: Clear Linux OS
Installed version: 33360
Version URL:
Content URL:

It’s not 404 ( but key not found )

Nope, it’s 404 with body content

Request URL:
Request Method:GET
Remote Address:
Status Code:
Referrer Policy:strict-origin-when-cross-origin

Try from a different referrer. Go here

And find the same link

From there it will open.

NoSuchKeyThe specified key does not

This is what I see when I opened the link you provided in the browser

I should not have put that link there. It only serves to confuse. I meant go into .org docs (the link above it) and open it from there. Meaning find said link on the swupd docs page and click it there.

You’ll find it under the heading

How it works

It will open from there, because of the referrer policy.

Some weird referrer protection stuff, I see.
Output something like this will be much helpful

Distribution:      Clear Linux OS
Installed version: 33370
Release URL:
Content URL:

Because if something goes wrong with auto-update turned on, I can clearly see the current state and what was updated in the current release with one shot command and click to url.

It always takes a little extra effort to ride the bleeding edge. There is profit in it too though. The best thing to do if you have the resources is to run your own mirror and/or put a CI container with tests for your own needs somewhere in your toolchain. You could run a basic container right on your workstation – and let it tell you when to update after testing your critical apps and runtimes and making sure they still work.