When deploying Node.js-based Azure Functions using GitHub Actions, you might face an issue with the Windows workflow. In the latest template, there is an issue in the build step where the actions/upload-artifact action fails to upload the artifact due to too many files. The problem is caused by the node_modules folder, which contains many files (even for a starter Azure Function project).
Read moreIn August 2024, GitHub announced it would exclude hidden files by default in the actions/upload-artifact GitHub Action. If you are using this action in your workflow, you should be aware of this change, as it might break your workflow. info Read more about it on the notice of upcoming deprecations and breaking changes in GitHub Actions runners blog post from GitHub.
Read moreIn the last weeks, I have been moving the Front Matter CMS documentation and APIs to different hosting providers. The documentation and APIs were hosted on Vercel, but they stopped their open-source program, which made me look for alternatives. I decided to move the documentation to Netlify and the APIs to Azure.
Read moreSome time ago I wrote a couple of articles about how you can automate the process of releasing your SharePoint Framework solutions. This was achieved by two custom Gulp tasks to upload the static assets and solution package and a complete Visual Studio Team Services build and release pipeline. This process already saved me a lot of time, but since some time ago, I noticed that I had to manually deploy the solution package to get the latest version activated.
Read more