Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release zip files naming convention #1664

Open
SelvinPL opened this issue Feb 20, 2025 · 2 comments
Open

Release zip files naming convention #1664

SelvinPL opened this issue Feb 20, 2025 · 2 comments
Labels
builds This affects the build process or release artifacts

Comments

@SelvinPL
Copy link

SelvinPL commented Feb 20, 2025

Consider using different naming (without using version in it) for zip packages
so: https://github.com/gbdev/rgbds/releases/latest/download/rgbds-win64.zip (of course now it's not working)
would always point to newer release without knowing the version number

check fx gbdk2020

https://github.com/gbdk-2020/gbdk-2020/releases/download/4.3.0/gbdk-win64.zip
points directly to 4.3.0
and
https://github.com/gbdk-2020/gbdk-2020/releases/latest/download/gbdk-win64.zip
also points to this release(becuase it is latest)

other examples:
https://github.com/bbbbbr/romusage/releases/download/v1.3.1/romusage-windows.zip
https://github.com/bbbbbr/romusage/releases/latest/download/romusage-windows.zip

@Rangi42 Rangi42 added the builds This affects the build process or release artifacts label Feb 20, 2025
@Rangi42
Copy link
Contributor

Rangi42 commented Feb 20, 2025

This sounds reasonable to me. @ISSOtm @avivace Is there anything depending on the current naming convention?

@ISSOtm
Copy link
Member

ISSOtm commented Feb 21, 2025

The point was to have each file self-identify, but the argument is compelling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
builds This affects the build process or release artifacts
Projects
None yet
Development

No branches or pull requests

3 participants