Skip to content

chore(internal): configure releases #129

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
merged 3 commits into from
Apr 16, 2025
Merged

chore(internal): configure releases #129

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7eb9185
chore(internal): configure releases
Apr 16, 2025
b0a523e
fix
Apr 16, 2025
6c89d13
Update create-releases.yml
meorphis Apr 16, 2025
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
4 changes: 2 additions & 2 deletions .github/workflows/create-releases.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
name: Create releases
on:
schedule:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: no biggie, but having a manual release trigger wouldnt hurt!

I think that's what the cron job in the python-sdk functionally does actually

- cron: '0 5 * * *' # every day at 5am UTC
push:
branches:
- main
Expand All @@ -26,6 +24,7 @@ jobs:
stainless-api-key: ${{ secrets.STAINLESS_API_KEY }}

- name: Set up Ruby
if: ${{ steps.release.outputs.releases_created }}
uses: ruby/setup-ruby@v1
with:
bundler-cache: false
Expand All @@ -34,6 +33,7 @@ jobs:
bundle install

- name: Publish to RubyGems.org
if: ${{ steps.release.outputs.releases_created }}
run: |
bash ./bin/publish-gem
env:
Expand Down
Loading