Skip to content

ci: fail release if gem manifest is out of date #127

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
cb-alish merged 2 commits into from
Jul 2, 2026
Merged

ci: fail release if gem manifest is out of date #127

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
273080d
ci: fail release if gem manifest is out of date
cb-alish Jul 2, 2026
126ea7a
Merge branch 'master' into ci/verify-gem-manifest-on-release
cb-alish Jul 2, 2026
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
14 changes: 14 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,20 @@ jobs:
fi
echo "✅ Tag matches gemspec version."

- name: Verify gem manifest is up to date
run: |
make update-manifest
if ! git diff --quiet -- chargebee.gemspec; then
echo "❌ Gem manifest in chargebee.gemspec is out of date."
echo "Some files tracked in the repo are missing from (or stale in) s.files,"
echo "which means they would not be packaged into the released gem."
echo "Run 'make update-manifest' locally and commit the updated chargebee.gemspec."
echo "----- diff -----"
git --no-pager diff -- chargebee.gemspec
exit 1
fi
echo "✅ Gem manifest is up to date."

- name: Build gem
run: gem build chargebee.gemspec

Expand Down
Loading