Skip to content

ci(relock): Trigger update lockfiles on release commit #3048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sl0thentr0py merged 1 commit into from
Aug 6, 2026
Merged

ci(relock): Trigger update lockfiles on release commit #3048

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion .github/workflows/update_lockfiles.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,25 @@ name: Update lockfiles

on:
workflow_dispatch:
push:
branches:
- master
# Releases update the path gemspecs and version files. Regenerate the
Comment thread
sentry[bot] marked this conversation as resolved.
# committed locks immediately after those changes land on master.
paths:
- "**/*.gemspec"
- "**/lib/sentry/**/version.rb"
schedule:
# Weekly: refresh pins so we keep getting security patches.
- cron: "0 4 * * 1"

permissions:
contents: write

concurrency:
group: update-lockfiles
cancel-in-progress: false

jobs:
update:
runs-on: ubuntu-latest
Expand Down Expand Up @@ -61,7 +73,8 @@ jobs:
fi

COMMIT_TITLE="ci: 🤖 Update pinned CI lockfiles"
BRANCH_NAME="lockfiles/update-$(date +%m-%d)"
SHORT_SHA="${GITHUB_SHA:0:12}"
BRANCH_NAME="lockfiles/update-$(date +%m-%d)-${SHORT_SHA}"

# Which gems changed: the top-level dir of each touched lock.
GEMS=$(git diff --cached --name-only -- '**/gemfiles/*.gemfile.lock' | cut -d/ -f1 | sort -u)
Expand Down
Loading