Skip to content

feat: golang: bump version of Golang#112

Merged
GordonBeeming merged 2 commits into
GordonBeeming:mainfrom
rbeuque74:golang
May 21, 2026
Merged

feat: golang: bump version of Golang#112
GordonBeeming merged 2 commits into
GordonBeeming:mainfrom
rbeuque74:golang

Conversation

@rbeuque74
Copy link
Copy Markdown
Contributor

Hello,
Small pull request to bump the version of Golang to the latest.

rbeuque74 and others added 2 commits May 13, 2026 11:23
Signed-off-by: Romain Beuque <556072+rbeuque74@users.noreply.github.com>
Snippet bumped GOLANG_VERSION but generated Dockerfile wasn't refreshed,
failing the Verify Generated Dockerfiles CI check.

Co-authored-by: Claude <noreply@anthropic.com>
@GordonBeeming GordonBeeming merged commit f3f3fab into GordonBeeming:main May 21, 2026
26 checks passed
GordonBeeming added a commit that referenced this pull request May 21, 2026
* ci: auto-regenerate Dockerfiles on PRs

Adds two GitHub Actions workflows that react when a PR changes
docker/snippets/, docker/images.json, or docker/generate-dockerfiles.ps1:

* regen-dockerfiles-push.yml — same-repo PRs only. Regenerates the
  Dockerfiles and pushes the result back to the PR branch. Permission
  scope: `contents: write`.
* regen-dockerfiles-comment.yml — fork PRs only. Runs the base branch's
  trusted generator against the head's snippet data (never executes head
  code), detects drift, and posts a comment telling the contributor what
  to run. Refuses entirely if the PR modifies generate-dockerfiles.ps1.
  Permission scope: `contents: read` + `pull-requests: write`.

The existing verify-generated-dockerfiles job in publish.yml stays as the
hard CI gate — these workflows are the auto-fixer / nudge layered on top,
so PRs like #112 (golang bump without regen) self-heal instead of
needing a maintainer to push the regen commit manually.

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: GitButler <gitbutler@gitbutler.com>

* fix(ci): detect untracked Dockerfiles and avoid spam comments

Address PR review feedback from Codex and Copilot:

* git diff --quiet ignored untracked files, so a new image entry in
  images.json would generate a brand-new docker/generated/Dockerfile.*
  that the drift check would miss — "No drift" would fire, the new
  file would never get committed (push workflow) or surfaced (comment
  workflow), and the existing verify-generated-dockerfiles job would
  fail without explanation. Switch both workflows to
  `git status --porcelain -- docker/generated`, which catches modified,
  deleted, and untracked entries in one shot. The comment workflow
  also appends a "Untracked new generated files" section to the diff
  stat so contributors see exactly what's new.

* The fork-comment workflow posted a fresh PR comment on every
  synchronize event, which would spam long-running PRs. Introduce
  .github/scripts/sticky-pr-comment.sh — a 30-line helper that finds
  a prior bot comment by HTML marker and PATCHes it in place,
  creating a new one only when none exists. Both comment paths
  (drift and generator-changed) now use it with the same marker so
  the same comment is recycled.

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: GitButler <gitbutler@gitbutler.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: GitButler <gitbutler@gitbutler.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants