grafana / grafana/plugin-ci-workflows

Check the "any" zip cases where we never publish them to GCOM

Open
#38 0 comments 0 reactions 1 assignee Claimed by @xnyo View on GitHub
Dominant language
Go
Stars
10
Forks
6
Avg merge
19h 51m
Merged PRs (30d)
97

Description

I wonder why we are building the "any" zip if we never publish it to GCOM, just for the github release?

e.g. https://grafana.com/api/plugins/alexanderzobnin-zabbix-app/versions/4.6.1 only has arch specific versions, same here https://grafana.com/api/plugins/grafana-github-datasource/versions/2.0.0

Github releases do contain the combined zips:
- https://github.com/grafana/grafana-zabbix/releases/tag/v4.6.1
- https://github.com/grafana/github-datasource/releases/tag/v1.9.2

I am ok with leaving it as is, just wondering why we are even doing this, it becomes a bit weirder with "frontend only" plugins:
- https://github.com/grafana/clock-panel/releases/tag/v2.1.8
Like why is there `grafana-clock-panel-2.1.1.any.zip` as well as `grafana-clock-panel-2.1.1.zip`?

_Originally posted by @tolzhabayev in https://github.com/grafana/plugin-ci-workflows/issues/36#issuecomment-2636066677_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.