Hey!

Over the long weekend, I wrote and published a blog post about how I moved
part of the release process to the development phase for the ASF project I
contribute to.
This change also automated what used to be a manual process, using GitHub
Actions.

The post specifically covers how we validate two of the ASF policies:
- Ensuring all files have the ASF header license, with help of Apache Rat
- Making sure all npm dependencies comply with the ASF Category A licenses

I hope you find the post helpful and that it might even give you some ideas
for your own project. Could even follow along and use the same GitHub
Action workflow.

If you've got any feedback or suggestions, let me know! Especially if
there's something unclear or missing. I'd be happy to update it.
For example, I'm beginning to think I should have titled it "Automating ASF
Policy Audits" instead. :D

Post:
https://www.erisu.dev/posts/automating-the-apache-release-audit-with-github-actions/

Reply via email to