HNHiroyuki Nakahatainblog.iroha1203.dev·21h ago · 21 min readTaming a 40-Minute Lean CI: Three Rounds, Three Wrong SuspectsOur Lean 4 + mathlib project used to spend 41 minutes in CI on every single PR. Today, the worst case — rebuilding the heaviest files from scratch — takes 12 minutes, and an ordinary PR finishes in a 23LT
ADAce Data Cloudinacedatacloud.hashnode.dev·23h ago · 4 min readHow to Trigger Claude Code from Issues and Pull RequestsTurning a short portrait clip into a believable talking video is less about clever prompting than about getting the inputs, timing, and async workflow right. This guide builds that pipeline with one f00
TCThankGod Chibugwum Oboboinactocodes.hashnode.dev·1d ago · 11 min readThe Flutter-to-DevOps Pipeline: How to Automate Play Store Deployments with GitHub ActionsMobile app deployment is one of the last frontiers where many engineering teams still rely on manual processes. A developer builds a release locally, signs it on their machine, uploads it through the 00
SNSachin Nandanwarinazureguru.net·5d ago · 6 min readFederated Credentials with User-Managed Identity to Access Azure Services through GitHub actionsThe tittle sounds confusing right ? So how to access Azure services with federated credentials that are tied with User Managed Identities ? Even I was skeptical if it is even possible because its more42N
OOnyiGlobal2025inonyiglobal2025.hashnode.dev·5d ago · 24 min read CI/CD on AWS EKS — GitHub Actions, Docker, ALB Ingress, Trivy, and Monitoring How I built a production-grade application delivery pipeline on AWS EKS If you think CI/CD means "run some scripts and push to production" — this article will change that perspective. Real CI/CD is a00
DMDavid Montesdeocaindavidmontesdeoca.dev·Jul 26 · 8 min readThe one where backups keep your latest posts on your GitHub profile up to dateA while ago I wrote a post about automatically adding my latest blog posts to my GitHub profile. The idea was simple: a GitHub Action would query Hashnode's public GraphQL API, grab my most recent pos20
ANakshay Nikhareinakshaynikhare.hashnode.dev·Jul 24 · 4 min readHow a Single beforeEach Killed Our CI for 36 HoursSix failed CI runs. Thirty-six hours of GitHub Actions time. Every run timing out at exactly the 6-hour limit. The culprit was one line in tests/setup.js. The Setup We were building a multi-tenant pla00
ADAlbert Deutouinblog-adeutou.hashnode.dev·Jul 22 · 8 min readSelf-Hosting Like a Pro, Part 4: Monitoring with Prometheus, Grafana and Loki, plus a CI/CD Pipeline That Actually WorksThe stack from Part 3 is live: multiple domains, isolated namespaces, TLS everywhere. But a production system you cannot observe is a production system you do not control. In this part we install a fu00
PKPrashant Koiralainblog.prashantkoirala.info.np·Jul 21 · 22 min readSoftware publishing is moving beyond long-lived tokensPublishing software used to depend on a secret. A maintainer created an API token in a package registry, copied it into a CI secret store, and allowed a workflow to use it every time a release was pub00
MSManu Shuklainecorpit.hashnode.dev·Jul 17 · 23 min read84 malicious npm versions in 6 minutes: the 2026 TanStack trusted-publishing breach and the CI config that stops it84 malicious npm versions in 6 minutes: the 2026 TanStack trusted-publishing breach and the CI config that stops it Summary. On 11 May 2026, between 19:20 and 19:26 UTC, an attacker published 84 malic00