Skip to content
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.

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

ci: upgraded ruby/setup-ruby action from version v1.152.0 to v1.178.0 #214

Merged
merged 4 commits into from
Jun 20, 2024

Conversation

desusai7
Copy link
Contributor

📋 Changes

  • upgraded ruby/setup-ruby action from version v1.152.0 to v1.178.0 to support ruby version 3.0.7

📎 References

https://github.com/auth0/SimpleKeychain/actions/runs/9581919093/job/26419770960

@desusai7 desusai7 requested a review from a team as a code owner June 19, 2024 12:33
@desusai7 desusai7 self-assigned this Jun 19, 2024
Widcket
Widcket previously approved these changes Jun 19, 2024
@desusai7 desusai7 enabled auto-merge June 19, 2024 14:28
@desusai7 desusai7 disabled auto-merge June 19, 2024 14:30
@@ -52,6 +52,8 @@ jobs:
- name: Upload coverage report
if: ${{ matrix.platform.os == 'iOS' }}
uses: codecov/codecov-action@ab904c41d6ece82784817410c45d8b8c02684457
with:
token: ${{ secrets.CODECOV_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

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

If the job uses a secret, we used to require an 'authorize' check to avoid running the job on third party PRs –so as to avoid leaking the secrets: https://github.com/auth0/auth0-flutter/blob/main/.github/workflows/main.yml#L175

I'd suggest checking with the team how you prefer to handle the usage of CI secrets going forward.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Got it, will add authorize step for now and will discuss internally within the team as well on handling secrets going forward.

@desusai7 desusai7 merged commit 5c16146 into master Jun 20, 2024
13 checks passed
@desusai7 desusai7 deleted the ci/upgrade_setup_ruby_action branch June 20, 2024 05:50
@desusai7 desusai7 restored the ci/upgrade_setup_ruby_action branch July 2, 2024 14:56
@desusai7 desusai7 deleted the ci/upgrade_setup_ruby_action branch July 2, 2024 14:58
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.

None yet

2 participants