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 builder should strip v from version tag #73

Closed
pfeerick opened this issue Jul 3, 2023 · 4 comments · Fixed by #93
Closed

release builder should strip v from version tag #73

pfeerick opened this issue Jul 3, 2023 · 4 comments · Fixed by #93

Comments

@pfeerick
Copy link
Member

pfeerick commented Jul 3, 2023

Version tags have the v present, but it seems like from past releases this hasn't been included in the filename. Until I've ascertained the collateral damage to Buddy and Companion that would result from leaving this, release.sh should strip it out.

@gonzalo-bulnes
Copy link
Contributor

Hi @pfeerick, is this still an issue?

Subsidiary question: is it safe to assume that the interface with Buddy and Companion is restricted to the GitHub releases page?

@pfeerick
Copy link
Member Author

pfeerick commented Jan 3, 2024

As far as I know - I've not looked any further into this. And yes, just via the releases API.

@gonzalo-bulnes
Copy link
Contributor

gonzalo-bulnes commented Jan 5, 2024

Checking if I'm understanding the issue correctly, and if I'm reading the code correctly:

  • The assets from the last release don't include the v in their names (e.g. edgetx-sdcard-sounds-cz-2.9.0.zip)
  • The current release.sh script does create ZIP files with the content of the VERSION variable in their names (code)
  • The VERSION variable does contains a prefix, e.g. v2.9.0 because the tags contain it (code, tag)

... does that mean that the last release wasn't created by the release workflow? (Or that the asset names were edited before upload?)

@pfeerick
Copy link
Member Author

pfeerick commented Jan 5, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants