chore: update cloverrose/pkgdep 0.1.0 to 0.2.0

[cloverrose]

Check List

• Read CONTRIBUTING.md
  • Read OSS Contribution Guide
• All commits are signed
  • This repository enables Require signed commits, so all commits must be signed
• Avoid force push
• Do only one thing in one Pull Request

[suzuki-shunsuke]

Basically, packages are updated automatically.

• chore: update cloverrose/pkgdep v0.1.0 to v0.2.0 #27526

[suzuki-shunsuke]

Anyway, thank you for your contribution.

[cloverrose]

Basically, packages are updated automatically.

Thank you. I'd like to know for future contributing, What is the standard lag of detecting update?

[suzuki-shunsuke]

That's a good question.

pkg.yaml is updated by aqua-registry-updater and GitHub Actions schedule workflow.

The workflow runs per 10 minutes.

aqua-registry/.github/workflows/update.yaml

Lines 5 to 6 in 9d0d823

	schedule:
	- cron: "*/10 * * * *"

About 50 150 packages are handled per workflow run.

• https:/aquaproj/aqua-registry-updater/blob/c6892fa7307ac5c01e5a8f4bbcc74836af906dcf/pkg/controller/config.go#L32
• https:/aquaproj/aqua-registry-updater/blob/c6892fa7307ac5c01e5a8f4bbcc74836af906dcf/pkg/controller/update.go#L93

• aqua-registry/aqua-registry-updater.yaml

  Line 1 in 9d0d823

  limit: 150

There are 1562 packages now.

• Count packages #19792 (comment)

(1562 / 150) * 10 / 60 = 1.7355555556

So the standard lag is about 5 ~ 6 2 Hours.

But note that even if pkg.yaml isn't updated, you can still use the latest version of packages.
pkg.yaml is just test data.