Skip to content

[Bug]: Version numbers inconsistent #3048

Open
@dhoepfl

Description

@dhoepfl

Before submitting your bug report, please confirm you have completed the following steps

Bug description

I had Version 4042 installed and got the message that there is a new version of Quicksilver available (4044).

After update it shows an alert that allows you to check the release notes.
These notes seem to no longer maintained. What’s a local copy of the changelog good for if it does not contain the latest information?

Same for the online version of the change log: The note to use GitHub for latest information does not say that the change log is no longer updated at all. The note should either clearly say so or the page should automatically forward the user to the GitHub version.

The (old) change log contained both, version number (2.5.1) and build number (4044), the GitHub releases page only shows the version number (2.5.1). In the update available alert only the build number is shown, the “More Info” button there also leads to the change log but you can no longer see what version you would update from and to.

Steps to reproduce

  1. Using an outdated version: Open Quicksilver Preferences
  2. Select section Application
  3. In the section “Updates”, click “Check Now”
  4. Note the shown update info “(4042 → 4044)”
  5. Select the “More Info” button
  6. Find version “4044”.

Expected behavior

  • The local copy of the change log should include all relevant release notes.
  • The change log (online) should also include the latest information or automatically forward to the page that does.
  • The same number should be used everywhere: Version number (2.5.1) or build number (4044). If both are required, both should be shown, e.g. as “2.5.1.4044”.

MacOS Version

macOS 15.4.1

Quicksilver Version

2.4.3 (4042), 2.5.1 (4044)

Relevant Plugins

No response

Crash Logs or Spindump

No response

Screenshots

No response

Additional info

Maybe GitHub actions could be used to automatically include the “What's Changed” section of the release build into the change log file?

Metadata

Metadata

Assignees

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