Author	SHA1	Message	Date
pat-s	5bade188c2	chore: pin bincraft 4.2.0 and drop superseded standalone r-minor workflow ... Bumps the bincraft git-tag pin and version guard from v4.1.1 to v4.2.0 across all .crow workflows, removes .crow/build-r-minor-sensitive-packages.yaml (now superseded by the integrated full + iterative flow), and drops its now-orphaned hook-exclude entries.	2026-06-13 21:45:18 +02:00
pat-s	771d642531	feat(updates): classifier-driven r-minor builds + per-minor index across platforms	2026-06-13 21:43:16 +02:00
automation-bot	81f585f7f5	chore(deps): update reg.devxy.io/docker.io/library/alpine docker tag to v3.24	2026-06-10 00:31:30 +00:00
pat-s	2ba6ab28f7	chore: bump to bincraft 4.1.1	2026-05-31 09:30:02 +02:00
pat-s	b1bed68898	refactor(ci): skip bincraft reinstall when image already has it (#72) ... ## Summary bincraft is baked into the build-env images, but every workflow still unconditionally calls `pak::pak("git::.../bincraft.git")` (~30–60s per job). Pin bincraft to a specific tag (currently `v4.0.2`) and guard the install on a version check. ``` - /opt/R/$R_VERSION/bin/R -q -e 'if (!requireNamespace("bincraft", quietly = TRUE) || packageVersion("bincraft") != "4.0.2") pak::pak("git::https://codefloe.com/rpkgs/bincraft.git@v4.0.2")' ``` - Image matches the pin → skip install entirely. - Image is missing bincraft or has a different version → install the pinned tag (covers both broken bakes and intentional version bumps). - Renovate customManager keeps the pin and the version-check string in sync whenever bincraft cuts a new tag (uses `git-tags` datasource against the bincraft repo). Touches 43 `.crow` YAMLs + `renovate.json`. Reviewed-on: #72	2026-05-28 12:37:58 +00:00
pat-s	494730be5d	feat(ci): purge CDN cache after process-updates runs (#71) ... ## Summary - `process_cran_updates()` ends with `upload_package_index()`, refreshing `src/contrib/PACKAGES{,.gz,.rds,.db}` in S3 — but no CDN purge follows. - The CDN was only purged by the daily `update-package-index-*` chain, so between cron runs the edge kept serving stale indexes. A binary that landed in S3 was effectively invisible to `install.packages()` until the index-update chain caught up. Adds the same `Purge CDN cache` step that `update-package-index-*` already uses, parameterized per platform/arch. The script and image are unchanged. Reviewed-on: #71	2026-05-28 11:50:04 +00:00
pat-s	8c5362b7ab	refactor: R_VERSION syntax	2026-05-27 22:36:09 +02:00
pat-s	6faa3772d1	refactor(ci): use multi-R-version images across workflows (#70) ... ## Summary - Switches all 64 `.crow/*.yaml` workflows, the `Justfile`, and the commented-out `build-all-versions-install-deps.yaml` template to the new multi-R-version container images. - Each image tag drops `-${R_VERSION}` (e.g. `build-env-alpine:3.22-4.5` → `build-env-alpine:3.22`); workflows pick an R version by calling `/opt/R/${R_VERSION}/bin/R` explicitly. - Pattern-1 workflows (hard-coded image tag) gain a single `R_VERSION:` env var per file. - Pattern-2 workflows (`build-all-versions-*`, matrix-driven) continue to receive `R_VERSION` via `crow pipeline create --var`. ## Platform → R_VERSION mapping | Platform | Image | R_VERSION | | --- | --- | --- | | alpine 3.22 / 3.23 | `build-env-alpine:3.{22,23}` | 4.5.3 | | ubuntu jammy / noble | `build-env-ubuntu:{jammy,noble}` | 4.4.3 | | redhat 8 / 9 | `build-env-redhat:{8,9}` | 4.4.3 | | redhat 10 | `build-env-redhat:10` | 4.5.3 | The `alpine-321` audit-only workflows fall back to `build-env-alpine:3.23` since no 3.21 image exists in the new scheme; the audits only query S3/CRAN, so the container OS does not affect correctness. ## Bug fixes folded in 1. All six `weekly-audit-missing-alpine-*.yaml` files were pinned to `alpine:3.23-4.5` regardless of platform. Now each one points at its own alpine image. 2. All fourteen `update-package-index-*.yaml` files were pinned to `build-env-ubuntu:noble-4.4` (or `noble-4.5` for `redhat-10-amd64`) regardless of platform. Now each one uses its own platform's image. 3. `process-updates-ubuntu-2404-{amd64,arm64}.yaml` had `R_VERSION` of `4.4` (no patch) baked into the tag. Aligned to `4.4.3`, matching the audit and rebuild counterparts. ## Smoke targets (post-merge) One workflow per shape, ready to dry-run: - `process-updates-alpine-322-amd64.yaml` - `weekly-rebuild-missing-redhat-9-amd64.yaml` - `weekly-audit-missing-ubuntu-2204-amd64.yaml` - `update-package-index-redhat-10-amd64.yaml` - `archive-missed-packages.yaml` - `build-all-versions-amd64.yaml` (with its install-deps predecessor) - `build-r-minor-sensitive-packages.yaml` ## Follow-ups (out of scope, surfaced during review) - `process-updates-redhat-10-{amd64,arm64}.yaml` set `codename = "rhel9"` in their `upload_package_index(...)` calls. Pre-existing bug — should be `"rhel10"`. The `update-package-index-redhat-10-*` counterparts already use `"rhel10"` correctly. - `update-package-index-redhat-8-amd64.yaml` is missing the `packageVersion("bincraft")` diagnostic line that every sibling file has. Pre-existing asymmetry between amd64 and arm64. ## Spec & plan - Spec: `docs/superpowers/specs/2026-05-25-multi-r-version-images-design.md` - Plan: `docs/superpowers/plans/2026-05-25-multi-r-version-images.md` Reviewed-on: #70	2026-05-26 08:51:27 +00:00
pat-s	5293967137	feat: run incremental package index update after each process-updates workflow ... Each process-updates workflow now calls upload_package_index at the end to update the PACKAGES files for its platform/arch immediately after builds complete. The full update-package-index cron should be rescheduled to weekly.	2026-04-15 10:13:16 +02:00
pat-s	e959d9743f	refactor: migrate to backblaze	2026-03-22 00:32:03 +01:00
pat-s	96e2ffede0	chore: run amd builds only on artemis	2026-03-17 19:46:49 +01:00
pat-s	1def662598	refactor: update build-env image names	2025-12-13 10:53:39 +01:00
pat-s	9a7c2ddf18	ci: remove ntfy	2025-10-30 21:14:10 +01:00
pat-s	510bff292a	ci: GIT_RO_TOKEN -> REPO_RO_TOKEN	2025-10-17 14:45:07 +02:00
pat-s	bbddf0c12c	refactor: switch to reg.devxy.io	2025-08-31 20:56:59 +02:00
pat-s	30753d8871	use new postgres db and user	2025-06-25 15:53:40 +02:00
pat-s	a402168274	fix: always reinstall bincraft	2025-06-11 20:40:56 +02:00
pat-s	9e00f4caa3	chore: update links, remove duplicated pak install	2025-06-11 20:18:24 +02:00
pat-s	321e3d3205	refactor: bincraftR -> bincraft	2025-06-08 15:39:54 +02:00
pat-s	4b2a2cc4a7	chore: use new images	2025-06-04 18:47:28 +02:00
automation-bot	79807717ef	chore(deps): update binwiederhier/ntfy docker tag to v2.12.0	2025-05-30 01:00:59 +00:00
pat-s	919c960479	fix: install path for bincraftR	2025-05-25 19:57:03 +02:00
pat-s	559fbeb257	set NTFY env vars	2025-05-02 10:15:12 +02:00
pat-s	16e773b655	feat: migrate to hel1 location	2025-04-29 16:48:57 +02:00
pat-s	32738444fc	also process removed	2025-03-27 08:52:23 +01:00
pat-s	f1c47ad0ae	back to normal interval	2025-03-26 19:00:56 +01:00
pat-s	11e08c982e	rebuild latest pkgs for the last 6 months	2025-03-26 15:39:29 +01:00
pat-s	251e6e7b87	always process the last 3 days	2025-03-23 16:27:32 +01:00
pat-s	7617c25713	process old packages	2025-03-23 08:08:02 +01:00
pat-s	da393da3ff	adjust to bincraftR 2.0.0	2025-02-28 10:54:09 +01:00
pat-s	df4d99d2c5	rename to .crow	2025-02-27 20:13:00 +01:00

Renamed from .woodpecker/process-updates-ubuntu-2204-amd64.yaml (Previous history)