Automate updating 3rd party licenses #82
Conversation
|
I'm purposefully not updating the 3rd party licenses, to have this scheduled action happen on |
|
@paulo-ferraz-oliveira I was more thinking something that just runs a build, we should get notified if it fails. If it fails, then we know we need to update the licenses. The thing that I guess makes me nervous about this is nodejs deps 😬 Maybe I'm overly concerned here? |
|
Hm. I'm not worried, since the dependencies are kept by the action container itself. In any case, we can always try and see how it goes, right? |
|
@paulo-ferraz-oliveira Fair enough. Just need to be sure to review commits before release :) Can you rebase this so it passes? |
Sure. On it. |
(once per day, at 12:00)
|
Some action results are stuck because |
|
https://github.com/erlef/setup-beam/actions/runs/1687446824 ran and didn't update anything. 😄 I assume it's because there's really nothing to update - we've updated the licenses very recently. |
Does this seem like a good enough option?
Closes #76.