Jekyll build broken

[tuananhle7]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d4d1r1668d2gf

AWS Region

us-east-1

Amplify Hosting feature

Deployments, Frontend builds

Describe the bug

My recent Jekyll build on AWS Amplify mysteriously fails with

sass-embedded-1.62.1-x86_64-linux-musl requires rubygems version >= 3.3.22,
                                    which is incompatible with the current version, 3.1.6

This didn't happen before and I don't know how to get this build to work.

This is the full build log: https://gist.github.com/tuananhle7/e00d20b4062e10bc2573280f053356ce

For reference, here is a build log for the last successful build: https://gist.github.com/tuananhle7/bef7bbd28b90c156689fc46a07d28b00

Please help.

Expected behavior

Described above.

Reproduction steps

Described above.

Build Settings

No response

Log output

# Put your logs below this line

Additional information

No response

[nadetastic]

Hi @tuananhle7 I'm currently working to reproduce this issue and will follow up as soon as I have some information. Thanks!

[nadetastic]

@tuananhle7 I was able to reproduce this error using the following sample project (which is the default from jekyll new.

However I resolved by changing my build settings and overriding bundler package and setting it to latest.

Could you give this a try and let me know if it works?

[tuananhle7]

It works now, thanks!

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.