-
Notifications
You must be signed in to change notification settings - Fork 701
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
ci: properly update metadata on nigthly releases #10756
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for another try! Why draft though? LGTM as is... Did you have a chance to test it on your fork? That's what I did in the past (although, I somehow thought it worked when in fact it didn't).
It's draft because I was testing it on my fork and it turns out that despite the names of the settings, this action also doesn't do the right thing. I'm going to try out one of the other ones from the ticket. I think this one has a good chance of working: https://github.com/marketplace/actions/nightly-release . It's used by logseq and I can see that their releases seem to update properly, although it was last updated in December so that's a bit odd |
9ea29ca
to
81d47c9
Compare
The updated version of this seems to be working on my fork 🎉 https://github.com/TeofilC/cabal/releases |
ae3d3d1
to
81d47c9
Compare
@geekosaur could you review this? |
Previously only the artifacts would be replaced and all the other information would stay the same as the original nightly release. Resolves #10537
81d47c9
to
af23627
Compare
Previously only the artifacts would be replaced and all the other
information would stay the same as the original nightly release.
Resolves #10537