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

github: fix automated tag release action #4755

Merged
merged 2 commits into from
Nov 4, 2022

Conversation

grondo
Copy link
Contributor

@grondo grondo commented Nov 2, 2022

This fixes the github workflow that does our auto-release on tags. There was an incorrect key used in the yaml, and also step that wasn't necessary anymore. Also, "upgrades" the softprops/action-gh-release action which was inadvertently downgraded by a recent commit.

Fixes #4751 (though we really won't know until the next tag)

Problem: The GitHub auto-release action has an incorrect key in the
workflow yaml, and also includes a step that doesn't do anything.

Rename the 'release_name' key to just 'name', and remove the prep
release step which is no longer necessary.
Problem: In commit 286df0a the
softprops/actions-gh-release was pinned to a "newer" release by git
hash, but this project seems to move the v1 tag to the latest release
in the v1.x series, so the version was actually downgraded. This came
with some bugs that have been fixed.

Revert the softprops/action-gh-release version to @v1.
@grondo
Copy link
Contributor Author

grondo commented Nov 2, 2022

@vsoch: you might want to check the "latest version" for softprops/action-gh-release in your github action updater, it seems like they currently move the v1 tag to point to the latest release? (See https://github.com/softprops/action-gh-release/tags), so the latest auto-update actually downgraded our version of that action.

@vsoch
Copy link
Member

vsoch commented Nov 2, 2022

Thanks will take a look! This PR looks okay otherwise!

@vsoch
Copy link
Member

vsoch commented Nov 2, 2022

@grondo the reason for this is that we only "trust" major versions (akin to v1) for the list of trusted repos (e.g,. github maintained like actions/checkout) and for untrusted, we require a semantic version. So the tool was honoring that preference here, and if we ran again we would just add this particular repository to be under trusted.

@grondo
Copy link
Contributor Author

grondo commented Nov 2, 2022

I get it, that makes sense!

@codecov
Copy link

codecov bot commented Nov 2, 2022

Codecov Report

Merging #4755 (d43e00d) into master (2effa8e) will increase coverage by 3.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4755      +/-   ##
==========================================
+ Coverage   80.06%   83.41%   +3.34%     
==========================================
  Files         414      414              
  Lines       69583    70011     +428     
==========================================
+ Hits        55712    58397    +2685     
+ Misses      13871    11614    -2257     
Impacted Files Coverage Δ
src/bindings/python/flux/job/JobID.py 85.71% <0.00%> (-14.29%) ⬇️
src/bindings/python/flux/memoized_property.py 88.88% <0.00%> (-11.12%) ⬇️
src/bindings/python/flux/message.py 76.04% <0.00%> (-8.85%) ⬇️
src/bindings/python/flux/resource/ResourceSet.py 88.69% <0.00%> (-7.54%) ⬇️
src/bindings/python/flux/job/wait.py 89.13% <0.00%> (-6.22%) ⬇️
src/bindings/python/flux/job/info.py 87.78% <0.00%> (-5.72%) ⬇️
src/bindings/python/flux/resource/list.py 88.57% <0.00%> (-5.37%) ⬇️
src/bindings/python/flux/job/Jobspec.py 84.05% <0.00%> (-5.20%) ⬇️
src/cmd/flux-admin.py 86.95% <0.00%> (-3.96%) ⬇️
src/bindings/python/flux/core/handle.py 92.20% <0.00%> (-3.74%) ⬇️
... and 218 more

Copy link
Member

@garlick garlick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wasn't clear if you were ready to merge this but FWIW LGTM.

@grondo
Copy link
Contributor Author

grondo commented Nov 4, 2022

Thanks, I've set MWP.

@mergify mergify bot merged commit af708a2 into flux-framework:master Nov 4, 2022
@grondo grondo deleted the github-release-fix branch November 4, 2022 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

github: release action failure
3 participants