Issues | Pull Requests | v2.0.0...v2.1.0
🎉 New Packages
- #2790 dagger/dagger: A portable devkit for CI/CD pipelines
- #1221 #2797 ziglang/zig: General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software
- Thanks to 4513ECHO
Others
#2809 Support scaleway/scaleway-cli >= v2.5.1. ref. scaleway/scaleway-cli#1809
#1230 #2787 #2789 Separate registry.yaml per package
Separate registry.yaml per package
registry.yaml on the repository root directory is generated with generate-registry.sh.
Don't edit it manually, and if you update registry.yaml in pkgs directory, don't forget to run generate-registry.sh.
$ bash generate-registry.shProblem to solve
Even if registry.yaml is updated, the change isn't tested in CI.
We have to set pull request label target:<package name> to test the changed package.
Solution
By seperating files per package, you can get the list of changed packages, so you can easily test the change in CI.
Example
https://github.com/aquaproj/aqua-registry/runs/5802561966?check_suite_focus=true
In this pull request, knqyf263/utern is updated then it is tested in CI properly.
[INFO] aqua-ci.yaml
registries:
- name: standard
type: local
path: registry.yaml
packages:
- name: suzuki-shunsuke/ci-info@v2.0.3
- name: rhysd/actionlint@v1.6.10
- import: pkgs/knqyf263/utern/pkg.yaml
[INFO] + aqua -c aqua-ci.yaml i --test
time="2022-04-02T23:51:14Z" level=info msg="create a symbolic link" aqua_version=1.3.0 link_file=/home/runner/.local/share/aquaproj-aqua/bin/utern new=aqua-proxy program=aqua
time="2022-04-02T23:51:14Z" level=info msg="download and unarchive the package" aqua_version=1.3.0 package_name=knqyf263/utern package_version=v0.1.5 program=aqua registry=standard
time="2022-04-02T23:51:14Z" level=info msg="download and unarchive the package" aqua_version=1.3.0 package_name=rhysd/actionlint package_version=v1.6.10 program=aqua registry=standard