- Add health check command for PostgreSQL service to ensure proper initialization
- Update waiting mechanism to use built-in TCP checks for improved reliability
- Modify output messages for clarity and include warnings for potential test failures
- Replace Kaniko with Docker Buildx for frontend and backend builds
- Add steps for setting up Docker Buildx and logging into the container registry
- Enhance caching strategy with cache-from and cache-to options
- Introduce PostgreSQL service for backend testing with health checks
- Include steps to install PostgreSQL client and wait for readiness
- Update the installation step for GCC to include checks for various package managers
- Improve error handling and output messages for GCC installation
- Modify test execution to conditionally enable CGO based on GCC availability
- Ensure compatibility with non-CGO builds by setting CGO_ENABLED appropriately
- Rename step to "Install CGO dependencies" and enhance the installation process for GCC
- Implement robust checks for GCC availability and installation verification
- Set CGO_ENABLED to 0 for all relevant steps to ensure compatibility with non-CGO builds
- Change step name to "Verify CGO dependencies" and implement a check for GCC availability
- Update environment variables to ensure CGO is enabled during Go module operations
- Allow the installation of GCC to continue on error for improved resilience
- Update .gitignore to selectively ignore pkg/ directories at the root level
- Modify CI workflow to verify all Go packages can be listed
- Introduce configuration management with a new config package, including loading environment variables
- Add comprehensive tests for configuration loading and environment variable handling
- Implement Neo4j database interaction functions with corresponding tests for data extraction
- Introduce a verification step for Go module setup to ensure proper configuration
- Add a build step to populate the Go module cache before running vet commands
- Maintain existing environment variable settings for consistency
- Replace Docker Buildx with Kaniko for frontend and backend builds
- Streamline image build and push steps with Kaniko action
- Enhance caching strategy by specifying cache registry for both frontend and backend
- Maintain Dockerfile and context paths for clarity and consistency
- Replace Kaniko commands with Docker Buildx for frontend and backend builds
- Implement Docker login and setup steps for improved authentication
- Enhance caching strategy by specifying cache-from and cache-to options
- Streamline Dockerfile and context paths for clarity and maintainability
- Update CI workflow to use Docker run commands for Kaniko instead of containerized execution
- Simplify Docker authentication setup by creating a temporary directory for config
- Ensure proper context and dockerfile paths are used for both frontend and backend builds
- Replace aevea/action-kaniko with direct Kaniko executor commands for frontend and backend builds
- Add Docker authentication setup for Kaniko
- Update Kaniko image version to v1.24.0 and enhance caching options
- Add missing dockerfile and context parameters for frontend and backend builds
- Update Kaniko action from @master to @v0.9.0 for stability
- Fix 'sed' and 'cat' command not found errors in CI pipeline
- Remove vendor mode approach, use regular Go modules
- Add GOPROXY and GOSUMDB environment variables
- Explicitly set GO111MODULE=on for all Go commands
- Remove unnecessary vendor step
- Add GO111MODULE=on to ensure module mode in CI
- Add go mod vendor step to generate vendor directory
- Use -mod=vendor flag for vet and test commands
- Fixes 'package not in std' error in Gitea CI
- Replace buildah with Kaniko for optimal containerd compatibility
- Kaniko is specifically designed for building in Kubernetes/containerd environments
- No package installation needed - Kaniko runs in its own container
- Maintains Harbor registry integration and caching capabilities
- Simplifies runner deployment by removing package management
Benefits:
- Native containerd support (no Docker daemon needed)
- No package installation in CI runners
- Optimized for Kubernetes environments
- Same Harbor registry functionality with cleaner architecture
- Better resource usage than DinD approach
- Replace Docker-based CI/CD with buildah for containerd compatibility
- Remove Docker-in-Docker setup from Gitea runner deployment
- Use buildah/podman which work natively with containerd runtime
- Install buildah and podman in runner container during startup
- Maintain Harbor registry integration and caching capabilities
Benefits:
- Native containerd compatibility (no Docker daemon needed)
- Lighter resource usage (no DinD overhead)
- Better integration with K3s containerd runtime
- Same Harbor registry functionality with cleaner architecture
- Add Docker CLI installation to frontend-build and backend-build jobs
- Gitea runner uses minimal image without Docker CLI pre-installed
- Docker daemon is available via DinD but CLI needs to be installed
- Fixes 'Unable to locate executable file: docker' error
This resolves the CI/CD build failures by ensuring Docker CLI is available
for the docker/build-push-action to work properly.
- Remove redundant GO111MODULE environment variable (default in Go 1.16+)
- Add cache: true to setup-go action for better performance
- Ensure go mod tidy and verify run before go vet
- Simplify workflow structure to match best practices
## 🛠️ Yarn v4 Migration & Fixes
### Deprecated Flag Replacement
- **Replaced ** with in Dockerfile and CI workflow
- **Updated Yarn v4 compatibility** across build and deployment pipelines
### Peer Dependency Resolution
- **Added missing vis-network peer dependencies**:
-
-
-
-
-
- **Resolved vis-network dependency conflicts** with proper peer dependency versions
### Package Updates
- **Updated @testing-library/dom** from ^8.19.0 to ^10.4.0 for React 18+ compatibility
- **Updated TypeScript** to 5.7.3 for latest features and bug fixes
- **Updated @tailwindcss/forms** to ^0.5.11 for better form styling
- **Updated @tailwindcss/postcss** to ^4.1.18 for PostCSS compatibility
## 🔍 Dependency Health Improvements
### Version Conflicts Resolved
- **Fixed @testing-library/dom version mismatch** that was causing peer dependency warnings
- **Aligned vis-network ecosystem** with compatible peer dependency versions
- **Updated build tooling** for Yarn v4 compatibility
### CI/CD Pipeline Updates
- **Modernized Docker builds** with Yarn v4 --immutable flag
- **Updated GitHub Actions workflows** to use correct Yarn v4 commands
- **Maintained immutable lockfile enforcement** for reproducible builds
## 📦 Technical Benefits
- **Zero peer dependency warnings** for production builds
- **Yarn v4 full compatibility** across all environments
- **Improved test infrastructure** with updated testing libraries
- **Enhanced development experience** with latest tooling versions
This commit ensures the project builds successfully with Yarn v4 and resolves all dependency conflicts while maintaining production stability.
- Remove go list -m and go list ./pkg/config diagnostic commands
- These were added for debugging but are causing CI failures
- go vet will catch the actual issues we need to fix
- Add || echo to prevent go list ./pkg/config from failing the step
- This was added as a diagnostic but shouldn't block the workflow
- go vet will still catch actual issues
- Remove cache: 'yarn' from setup-node action as yarn isn't available yet
- Corepack will handle yarn installation after Node.js setup
- Fixes error where setup-node tries to use yarn before it's installed
- Add corepack enable step before yarn commands
- Corepack comes with Node.js and manages package managers
- Fixes 'Unable to locate executable file: yarn' error
- Required for Yarn 4 (Berry) specified in package.json
- Update Dockerfile from golang:1.21 to golang:1.25.3 to match go.mod
- Update Dockerfile.dev from golang:1.25 to golang:1.25.3 for consistency
- Add GO111MODULE=on to all Go-related CI steps for explicit module mode
- Ensures all environments (CI, Docker, local) use Go 1.25.3 consistently
- Set GO111MODULE=on explicitly to ensure module mode
- Add go list -m and go list ./pkg/config to verify module recognition
- This should help diagnose why Go isn't recognizing the module in CI
- Run go build before go vet to ensure Go recognizes the module structure
- This should fix the 'package not in std' error by initializing the module properly
- Update CI workflow to use go-version 1.25.3 instead of 1.23
- Keep go.mod at 1.25.3 to match project requirements
- Fixes version mismatch that caused 'package not in std' errors
