Skip to content

feature_request(option): “api: latest” #582

@Kristinita

Description

@Kristinita

1. Summary

It would be nice if the value of the api option could specify the latest version of the Browser Update API.

2. Example of desired behavior

For example, I set api: latest.

  1. At the time of writing this issue, the latest version of the Browser Update API is 2024.02. This month api: latest is the same as api: 2024.02.
  2. Next month, the latest version of the Browser Update API may be 2024.03. api: latest automatically becomes the same as api: 2024.03. And so on.

3. Reasons why the feature is needed

  1. For Browser Update users. I’m used to using new versions of libraries, scripts, programs, and so on. Currently, to use the new version of the Browser Update API, users must manually update the api setting value. This wastes their time, and they may forget to update the value. It would be nice if it would be possible to get the latest version automatically, without any manual intervention.
  2. For Browser Update developers. The more people who use the latest version of the Browser Update API, the more likely it’s that someone will report bugs and/or another problems with the latest version, not with older versions. Possibly, most Browser Update users don’t closely monitor Browser Update updates and may not change the Browser Update configuration file, including the api parameter, for years. The Browser Update developers may not be aware of problems with the latest version since perhaps I think there are hardly many users regularly update the value of the api option.

Thanks.

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