Skip to content

Latest commit

 

History

History
56 lines (37 loc) · 2.9 KB

File metadata and controls

56 lines (37 loc) · 2.9 KB

Contributing

We don't accept pull requests from contributors. As described in README.md, most of files are automatically maintained. And we maintain the automation tools like GitHub Actions and ar2. Please create an issue if you have any problem.

This document is for outside contributors. For maintainers, see MAINTAINING.md.

For non-aqua users

aqua-registry-g2 is a registry for aqua, not for other tools. So we don't accept bug reports that haven't been reproduced using aqua. If you face a problem using another tool, please ask that tool's community for help first, and confirm that you can reproduce the problem using aqua before creating an issue in this repository. If you can, please create an issue using the issue template.

Background

As of 2026-09-27, other tools like mise, Docker Agent, Atmos, and Dagu use aqua-registry.

References:

As a result, users of these tools sometimes report issues that can't be reproduced using aqua, and we can't address them.

How To Add packages

Create a GitHub Issue from the issue template.

How To Support a new version

registry.json is automatically created by GitHub Actions via schedule event. So please wait for a while. The mutable versions like latest, develop, and nightly aren't supported.

How To Fix index.json

index.json is automatically updated by GitHub Actions via schedule event.

How To Fix names.json

names.json is automatically updated via GitHub Actions. So we don't need to fix it manually. It is rendered from index.json, so a missing alias is a missing alias in the package's registry.yaml.

A repository transfer needs nothing. We notice the repository answering to another name, rename the package to that name, and keep the old one as an alias, so a configuration still asking for it keeps working. This takes two steps that run on their own schedules, so please wait for a while.