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

ruby 3.4: Bump gems for released ruby batch 6 #38533

Merged

Conversation

justinvreeland
Copy link
Member

No description provided.

@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 30, 2024
@justinvreeland justinvreeland force-pushed the jvreeland/bump-gems-batch-6 branch 10 times, most recently from cd0e5f3 to 8de3b8d Compare January 2, 2025 15:07
@justinvreeland
Copy link
Member Author

Not sure why this PR is taking so long to build. I'll be splitting it into smaller pieces instead.

@justinvreeland justinvreeland force-pushed the jvreeland/bump-gems-batch-6 branch from 8de3b8d to 982f18e Compare January 2, 2025 18:02
@justinvreeland
Copy link
Member Author

It really does seem like the gems in #38631 were causing the huge time issues.

@justinvreeland justinvreeland marked this pull request as ready for review January 2, 2025 18:17
@imjasonh imjasonh merged commit 2dfea58 into wolfi-dev:main Jan 2, 2025
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants