Skip to content

update using bundle update #601

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

Merged
merged 1 commit into from
Oct 18, 2016
Merged

update using bundle update #601

merged 1 commit into from
Oct 18, 2016

Conversation

jarrodu
Copy link
Member

@jarrodu jarrodu commented Oct 18, 2016

Okay.

I started with a master branch that is up to date. That is I git pull etc.

I then ran;

bundle update

Only two files where modified. Gemfile.lock and .bundle/conf.

Then I checked the version of jekyll.

bundle exec jekyll --version

and I get jekyll 3.2.1.

You can also see that in the Gemfile.lock file many other gems have been updated as well.

The point of this is that the actual Gemfile, opposed to the Gemfile.lock file, was not changed. It is working exactly has it should be. It keeps our site working with the same versions of all the gems as is used on gh-pages.

Also note that the gh-pages gem was automatically updated as well. 46 -> 98 :-)

@SethTisue
Copy link
Member

awesome

@SethTisue SethTisue merged commit 8b1bc02 into scala:master Oct 18, 2016
@SethTisue
Copy link
Member

The point of this is that the actual Gemfile, opposed to the Gemfile.lock file

got it. understand now

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.

2 participants