Skip to content

Suggestion: make release files consistent #7470

Closed
Closed
Suggestion: make release files consistent#7470
Labels
discussFeature changes that require discussion primarily among the GitHub CLI teamneeds-investigationCLI team needs to investigate

Description

@mway
mway
opened on May 19, 2023

Release filenames just changed, and are "humanized" names. Would it be possible to go back to typical space-less, uname-based releases with file extensions (which are far more widely used)? The new structure makes it difficult to programmatically generate URLs to download releases.

Thanks for your consideration!

Activity

  1. mway
    added
    feedback
    on May 19, 2023
  2. cliAutomation
    added
    needs-triageneeds to be reviewed
    on May 19, 2023

  3. vilmibm commented on May 19, 2023

    @vilmibm
    vilmibm
    on May 19, 2023
    Contributor

    At first I thought this was a global change to the GitHub web UI but I'm wondering if it's something that changed with the recent work on our deployment flow? @mislav do you know? I definitely think raw filenames should be shown and not anything humanized.

  4. vilmibm
    added
    needs-investigationCLI team needs to investigate
    discussFeature changes that require discussion primarily among the GitHub CLI team
    and removed
    needs-triageneeds to be reviewed
    on May 19, 2023

  5. mway commented on May 19, 2023

    @mway
    mway
    on May 19, 2023
    Author

    I originally noticed this because I made a request for an incorrectly generated URL - it looks like you're just specifying custom asset names but the underlying URL is correct.

    For example, the asset named GitHub CLI 2.29.0 linux amd64 has the URL https://github.com/cli/cli/releases/download/v2.29.0/gh_2.29.0_linux_amd64.tar.gz - I had just seen the 404 on my end, checked the releases page, saw that the asset names didn't appear to be filenames (which is atypical IME), and assumed that the URLs were broken.

    Apologies for not looking harder first. :)

  6. mway
    closed this as completedon May 19, 2023

  7. mislav commented on May 22, 2023

    @mislav
    mislav
    on May 22, 2023
    Contributor

    @vilmibm is right in that the latest deployment changes, we've added human labels to all our release assets. The asset filenames themselves have not changed, except the macOS tar.gz that was changed into a zip for notarization reasons.

    Ref. #7324

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussFeature changes that require discussion primarily among the GitHub CLI teamneeds-investigationCLI team needs to investigate

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions