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

feat(ruby): updating semantic-release-rubygem-with-pkg-root for releasing rubygems #8

Merged
merged 2 commits into from
Sep 10, 2020

Conversation

billxinli
Copy link
Contributor

Adding ruby and bundler for building ruby based gems.

Dockerfile Outdated

COPY package.json package-lock.json index.js /action/
RUN npm ci --only=prod

RUN useradd -ms /bin/bash deploy
USER deploy
Copy link
Owner

Choose a reason for hiding this comment

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

this does nothing in GitHub actions as they are always run as root

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Without it bundler will complain about being run with root. But gem will still build, it really just ensures that Gem lock will have the latest version as the gem itself.

[8:17:38 PM] [semantic-release] [semantic-release-rubygem-with-pkg-root] › ℹ  Updating lock file with command `bundle install`
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.

@ahmadnassri ahmadnassri merged commit f970698 into ahmadnassri:master Sep 10, 2020
@github-actions
Copy link

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions github-actions bot added the released This change has been released label Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released This change has been released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants