- 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
