v0.1.26

k6registry v0.1.26 is here 🎉!

This is an internal maintenance release.

Fix change detection

The use of the out parameter was a prerequisite for change detection in GitHub Actions mode. If the api parameter is used, the out parameter is not required. As a result, when using the api parameter, change detection did not work until now. This issue is fixed in this release. Change detection now works when using the api parameter in GitHub Actions mode.

v0.1.25

k6registry v0.1.25 is here 🎉!

This is an internal maintenance release.

Added testability of generated files

The generated registry and catalog will play an important role in the k6 binary provisioning subsystem, so it is important that there is no loss of service due to generated files. It is advisable to test the generated files to see if they meet the minimum requirements.

The --test flag can be used to test registry and catalog files generated with the --api flag. The test is successful if the file is not empty, contains k6 and at least one extension, and if all extensions meet the minimum requirements (e.g. it has versions).

v0.1.24

k6registry v0.1.24 is here 🎉!

This is an internal maintenance release.

Added testability of generated files

The generated registry and catalog will play an important role in the k6 binary provisioning subsystem, so it is important that there is no loss of service due to generated files. It is advisable to test the generated files to see if they meet the minimum requirements.

The --test flag can be used to test registry and catalog files generated with the --api flag. The test is successful if the file is not empty, contains k6 and at least one extension, and if all extensions meet the minimum requirements (e.g. it has versions).

v0.1.23

k6registry v0.1.23 is here 🎉!

This is an internal maintenance release.

Fix cache saving issue

The GitHub workflow is running with user id 1001 and group id 127. The k6registry docker container runs with the default user id in debian. As a consequence, the cache directory created under XDG_CACHE_HOME fails to save.

The solution is to use the same user id and group id as the GitHub workflow in the k6registry docker container (user id: 1001, group id: 127).

v0.1.22

k6registry v0.1.22 is here 🎉!

This is an internal maintenance release.

Retry git pull on error

In the git working directory, the file permissions are changed to make the cache persistent in GitHub action mode. As a consequence, the git pull operation will fail (if permissions have actually been changed).

To fix this, if the pull operation fails, the pull operation is repeated after a forced checkout operation.

v0.1.21

k6registry v0.1.21 is here 🎉!

This is an internal maintenance release.

Retry git pull on error

In the git working directory, the file permissions are changed to make the cache persistent in GitHub action mode. As a consequence, the git pull operation will fail (if permissions have actually been changed).

To fix this, if the pull operation fails, the pull operation is repeated after a forced checkout operation.

v0.1.20

k6registry v0.1.20 is here 🎉!

This is an internal maintenance release.

Added verbose logging

• CLI: added the -v/--verbose flag for verbose logging
• GitHub action: added verbose input parameter for verbose logging

v0.1.19

k6registry v0.1.19 is here 🎉!

This is an internal maintenance release.

simplify responsibility*

• only use registry.schema.json instead of owning it, registry.schema.json source moved to grafana/k6-extension-registry repository
• only implement openapi.yaml and not own it, openapi.yaml source moved to grafana/k6-extension-registry repository

v0.1.18

k6registry v0.1.18 is here 🎉!

This is an internal maintenance release.

extension catalog support*

The registry and the catalog contain the same elements, only in different containers. The registry is a list (array), and the catalog is a map (object).

The consequence of this is that the versions property is moved from the repository object to the extension object.

During the generation of registry subsets, catalogs are also generated for the subsets (e.g. cloud.json and cloud-catalog.json).

v0.1.17

k6registry v0.1.17 is here 🎉!

This is an internal maintenance release.

Fix file/directory permissions

In GitHub Action mode, the permissions of the cache (XDG_CACHE_HOME) files have been corrected.

In the case of files, now the permission set to 0o644, in the case of a direcotry to 0o755.