blog.naokihaba.com

OSS activity in June 2026

In June, I sent a PR to add GitLab CI/CD support to setup-vp. I also sent PRs about the warnings for Git hooks in vp migrate.

voidzero-dev/setup-vp

feat: add GitLab CI/CD integration for setup-vp (#97)

setup-vp only supported GitHub Actions. So a team that used GitLab had to write the Vite+ install steps by hand (#88). GitLab receives inputs and sets PATH in a different way from GitHub Actions. So the existing code cannot be used as it is.

So, before I wrote the code, I wrote an RFC. I also made a diagram of how setup-vp runs on GitLab. After I discussed the approach, I implemented it. It was merged on July 5.

Comparison of how setup-vp runs in GitHub Actions and GitLab CI/CD. GitHub Actions calls it with uses, receives the with values, runs with the Node.js that GitHub provides, adds PATH by using the GitHub Actions mechanism, and saves the cache in a post step. GitLab calls it with include remote and extends, receives spec:inputs as SETUP_VP_* environment variables, runs with the Node.js in the image through bootstrap.sh, adds PATH in bootstrap.sh, and handles the cache in the GitLab settings. vp install is the same for both.

voidzero-dev/vite-plus

docs(migrate): clarify Git hook tool migration (#1901)

For projects that use simple-git-hooks, lefthook, or yorkie, vp migrate skips the pre-commit migration and shows a warning (#1854). The reason was written only in the RFC. So I added an explanation to the migration guide.

This is a follow-up to #1901. I added a link to the vp migrate warning. The link takes readers to the relevant section of the migration guide.