Skip to content

fix(ci): clear Push Gem Node 20 and cache warnings - #31

Merged
proxymesh merged 1 commit into
mainfrom
cursor/fix-push-gem-ci-warnings-4f36
Sep 1, 2026
Merged

fix(ci): clear Push Gem Node 20 and cache warnings#31
proxymesh merged 1 commit into
mainfrom
cursor/fix-push-gem-ci-warnings-4f36

Conversation

@proxymeshai

Copy link
Copy Markdown
Collaborator

Summary

Addresses the annotations from Push Gem run 33556057220:

  • Gem release succeededruby-proxy-headers 0.2.3 was pushed and is live on RubyGems (Successfully registered gem: ruby-proxy-headers (0.2.3)).
  • Node.js 20 deprecation — bump rubygems/release-gem from v1.2.0 → v1.4.1, which pulls in configure-rubygems-credentials on Node 24.
  • Cache write deniedworkflow_run gets a read-only Actions cache token for the default branch, so skip bundler-cache on that trigger (keep it for release / workflow_dispatch).

Test plan

  • PR CI (unit + integration) passes
  • Next gem push via workflow_run should no longer show the Node 20 or cache-write annotations

Slack Thread

Open in Web Open in Cursor 

Bump rubygems/release-gem to v1.4.1 so configure-rubygems-credentials
runs on Node 24, and skip bundler-cache on workflow_run where Actions
cache is read-only for the default branch.

Co-authored-by: ProxyMesh AI <proxymeshai@users.noreply.github.com>
@proxymesh
proxymesh marked this pull request as ready for review September 1, 2026 20:40
@proxymesh
proxymesh merged commit 09a7dc4 into main Sep 1, 2026
4 checks passed
@proxymesh
proxymesh deleted the cursor/fix-push-gem-ci-warnings-4f36 branch September 1, 2026 20:40
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