You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Rene Cannao 78f06fcade ci: fix macOS package naming and release upload ... The 6 macOS workflows had three interacting bugs: 1. All three tier variants (stable/v31/genai) produced tarballs with the same filename (proxysql-${GIT_VERSION}-macos-<arch>.tar.gz), where GIT_VERSION came straight from `git describe`. The Makefile bumps the version for v31/genai builds, but the workflow did not mirror that — so a v3.1 or v4.0 binary was packaged under a 3.0.x name. 2. `gh release upload --clobber` then overwrote the tarballs of the sibling tier jobs racing on the same filename, leaving only one surviving macOS artifact per arch across the three tiers. 3. `gh release create v3.0-head --draft 2>/dev/null || true` spawned extra duplicate drafts, and `gh release upload v3.0-head` picked a non-deterministic draft (often a stale SHA) rather than the canonical current-SHA draft used by the Linux package workflows. Fixes, matching the Linux CI-package-* workflows: - Add an `init_release` job that finds or creates the canonical draft for the current SHA+tag via a race-tolerant lowest-id-wins loop, and passes RELEASE_ID to the build job. - Compute the tarball version by mirroring the Makefile's tier bump (major+1 for GENAI, minor+1 for 31), so artifacts are named proxysql-3.0.8-…, proxysql-3.1.8-…, proxysql-4.0.8-… — consistent with the Linux RPM/DEB naming convention. - Upload by release ID with per-asset delete-if-exists, eliminating cross-tier clobber and stale-draft targeting.		2 months ago
..
ISSUE_TEMPLATE	Update issue templates	1 year ago
workflows	ci: fix macOS package naming and release upload	2 months ago
CLA.md	Add Contributor License Agreement (ICLA + CCLA) for CLA assistant	2 months ago
issue_template.md	Rewrite and formatting change to issue template	6 years ago