- Add repository setup to CI workflow before installing dependencies
- Add repository setup to Dockerfile for composefs package
- Use correct repository key URL and sources.list format
- This allows CI to install composefs from private particle-os registry
- Add composefs to CI dependencies (available in particle-os registry)
- Add composefs to package dependencies in control file
- Add composefs to Dockerfile
- Composefs is available as composefs=0.1.0++ in the registry
- Add check to only rename if old and new names are different
- Prevents 'mv: same file' error when package already has build version
- Package is already correctly named with build version from dpkg-deb
- This should complete the CI successfully
- Change package detection from ../*.deb to *.deb (current directory)
- dpkg-deb --build creates packages in current directory, not parent
- Update package processing logic to use mv instead of cp
- This should fix the 'No Debian package found' error
- Remove debian/ directory check that was causing failure
- Create debian/ directory if it doesn't exist
- Update error messages to only check for Cargo.toml
- This matches the apt-ostree CI pattern
- Revert to manual git clone like apt-ostree CI
- Use correct repository name: apt-ostree-builder (not bootc-image-builder)
- Update all git clone commands to use correct repo URL
- Disable extra workflow files to focus on main ci.yml
- Remove composefs from CI dependencies (not available in Debian)
- Update package control file to remove composefs dependency
- Update Dockerfile to remove composefs
- Update CI summary to reflect correct dependencies
- Update dependencies to match bootc-image-builder requirements
- Fix package name references from apt-ostree-builder to bootc-image-builder
- Update package description and dependencies
- Fix CI summary and artifact references
