Skip to content

Conversation

@alexeagle
Copy link
Member

@alexeagle alexeagle commented Dec 6, 2024

Forked PR from #33 (I don't have permission to push to that branch)

fixes #32

What is this?

This PR fixes filename resolution for release candidate version of protoc. RC names like 29.0-rc3 have release artifacts with names like 29.0-rc-3.... see the release assets for 29.0-rc3 or 28.0-rc2

Changes are visible to end-users: no

Test plan

  • Pretty much covered by existing test cases with example protoc version changed to LATEST
  • Added unit test to validate release_version -> artifact_name against supported versions

@alexeagle alexeagle requested a review from thesayyn December 6, 2024 19:48
@alexeagle alexeagle merged commit 2782f68 into main Dec 6, 2024
8 checks passed
@alexeagle alexeagle deleted the aaylward branch December 6, 2024 20:04
@aaylward
Copy link
Contributor

aaylward commented Dec 6, 2024

Thanks!

@aaylward
Copy link
Contributor

aaylward commented Dec 9, 2024

@alexeagle was this meant to be part of the 0.3.5 release? I don't see the change there

@alexeagle
Copy link
Member Author

alexeagle commented Dec 9, 2024

Oh thank you - I tagged 0.3.5 at the same commit as 0.3.4. Good thing I'm rolling out automation to prevent that mistake in a manual release step!

To github.com:aspect-build/toolchains_protoc.git
 * [new tag]         v0.3.6 -> v0.3.6

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 this pull request may close these issues.

[Bug]: Examples fail to build with v29.0-rc3 or LATEST (when LATEST is a release candidate)

4 participants