Can bundler show me which gems in Gemfile have newer versions (eg. dry-run of bundle update)

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

Is there a way to run bundle update in pretend mode, similar to the -p (pretend) flag for Rails generators or cap's -n (dry-run) flag?

I'm imagining something like:

$> bundle update -p

Fetching source index for http://rubygems.org/

The following gems have updated versions:

...

list of gems

...

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

I was searching for something like that just a few days ago too, but so far no luck. Hopefully they'll something like soon if it does not exist yet.

– coder_tim
Jan 15 '11 at 0:45

add a comment |

Is there a way to run bundle update in pretend mode, similar to the -p (pretend) flag for Rails generators or cap's -n (dry-run) flag?

I'm imagining something like:

$> bundle update -p

Fetching source index for http://rubygems.org/

The following gems have updated versions:

...

list of gems

...

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

I was searching for something like that just a few days ago too, but so far no luck. Hopefully they'll something like soon if it does not exist yet.

– coder_tim
Jan 15 '11 at 0:45

add a comment |

Is there a way to run bundle update in pretend mode, similar to the -p (pretend) flag for Rails generators or cap's -n (dry-run) flag?

I'm imagining something like:

$> bundle update -p

Fetching source index for http://rubygems.org/

The following gems have updated versions:

...

list of gems

...

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

Is there a way to run bundle update in pretend mode, similar to the -p (pretend) flag for Rails generators or cap's -n (dry-run) flag?

I'm imagining something like:

$> bundle update -p

Fetching source index for http://rubygems.org/

The following gems have updated versions:

...

list of gems

...

ruby bundler

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

edited Mar 28 '18 at 0:40

Dave Powers

580921

edited Mar 28 '18 at 0:40

Dave Powers

580921

edited Mar 28 '18 at 0:40

Dave Powers

580921

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

asked Jan 14 '11 at 23:13

Jeff Poulton

5,30211712

I was searching for something like that just a few days ago too, but so far no luck. Hopefully they'll something like soon if it does not exist yet.

– coder_tim
Jan 15 '11 at 0:45

add a comment |

I was searching for something like that just a few days ago too, but so far no luck. Hopefully they'll something like soon if it does not exist yet.

– coder_tim
Jan 15 '11 at 0:45

I was searching for something like that just a few days ago too, but so far no luck. Hopefully they'll something like soon if it does not exist yet.

– coder_tim
Jan 15 '11 at 0:45

add a comment |

3 Answers
3

active

oldest

votes

Bundler 1.1 introduced a new 'outdated' feature, which is exactly what I was looking for. Pat Shaughnessy has a great write-up on the new features. In his words, bundle outdated:

displays the gems it would download and install, but without actually
doing it. This gives me the freedom to inspect the list and update
just the gems I would like to.

This should make it a snap to see what gems are due for an update without actually modifying your source and local gems. Thanks Bundler!

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

7

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

2

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

6

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

add a comment |

$ bundle update

$ git diff Gemfile.lock

$ git checkout Gemfile.lock

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

2

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

add a comment |

I was looking specifically for how to only show the outdated gems that are in my gemfile. Looks like this does it: bundle outdated --only-explicit

That will 'Only list gems specified in your Gemfile, not their dependencies'

Source: https://bundler.io/man/bundle-outdated.1.html

Hopefully this is helpful for someone else.

answered Jan 4 at 0:00

Chnikki

60117

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f4696932%2fcan-bundler-show-me-which-gems-in-gemfile-have-newer-versions-eg-dry-run-of-bu%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

Bundler 1.1 introduced a new 'outdated' feature, which is exactly what I was looking for. Pat Shaughnessy has a great write-up on the new features. In his words, bundle outdated:

displays the gems it would download and install, but without actually
doing it. This gives me the freedom to inspect the list and update
just the gems I would like to.

This should make it a snap to see what gems are due for an update without actually modifying your source and local gems. Thanks Bundler!

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

7

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

2

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

6

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

add a comment |

Bundler 1.1 introduced a new 'outdated' feature, which is exactly what I was looking for. Pat Shaughnessy has a great write-up on the new features. In his words, bundle outdated:

displays the gems it would download and install, but without actually
doing it. This gives me the freedom to inspect the list and update
just the gems I would like to.

This should make it a snap to see what gems are due for an update without actually modifying your source and local gems. Thanks Bundler!

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

7

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

2

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

6

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

add a comment |

Bundler 1.1 introduced a new 'outdated' feature, which is exactly what I was looking for. Pat Shaughnessy has a great write-up on the new features. In his words, bundle outdated:

displays the gems it would download and install, but without actually
doing it. This gives me the freedom to inspect the list and update
just the gems I would like to.

This should make it a snap to see what gems are due for an update without actually modifying your source and local gems. Thanks Bundler!

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

Bundler 1.1 introduced a new 'outdated' feature, which is exactly what I was looking for. Pat Shaughnessy has a great write-up on the new features. In his words, bundle outdated:

displays the gems it would download and install, but without actually
doing it. This gives me the freedom to inspect the list and update
just the gems I would like to.

This should make it a snap to see what gems are due for an update without actually modifying your source and local gems. Thanks Bundler!

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

answered Nov 22 '11 at 5:03

Jeff Poulton

5,30211712

7

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

2

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

6

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

add a comment |

7

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

2

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

6

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

It seems like bundle outdated will show newer versions of gems, but won't take into account the version limits specified in your Gemfile, so it may not display the same results as a full update. For example, I have gem 'rails', '~> 3.1.3' specified in my Gemfile, and bundle update rails works as expected, but bundle outdated shows * rails (3.2.8 > 3.1.3).

– Alex Michaud
Nov 6 '12 at 1:16

@zole, that can be seen as either an advantage or disadvantage. For example, I usually specify the gem versions for every gem, so bundle outdated would be useless for me if it looked at those versions. But for someone like you who only limits some gems' versions, you would be better off with version checking. So I think an optional argument would be the solution for both our cases.

– Cristian
Dec 9 '13 at 8:26

Looks like the --strict option was added in version bundler v1.5. I have just tried it out and it seems to work like @zole was expecting. Source: bundler.io/v1.7/bundle_outdated.html

– complistic
Jan 12 '15 at 5:28

sometimes even a gem is up to date, it can be no longer in active development(abandoned project). is there any way to list down release dates of the gems?

– Oshan Wisumperuma
Dec 21 '18 at 7:29

add a comment |

$ bundle update

$ git diff Gemfile.lock

$ git checkout Gemfile.lock

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

2

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

add a comment |

$ bundle update

$ git diff Gemfile.lock

$ git checkout Gemfile.lock

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

2

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

add a comment |

$ bundle update

$ git diff Gemfile.lock

$ git checkout Gemfile.lock

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

$ bundle update

$ git diff Gemfile.lock

$ git checkout Gemfile.lock

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

answered Jan 15 '11 at 3:21

yfeldblum

59.4k8120161

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

2

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

add a comment |

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

2

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

This is nowhere near an answer to the question. OP asks about "bundler"; this answer provides a hacky solution that has nothing to do with bundler's functionality.

– 1.44mb
Sep 4 '15 at 23:13

Your comment is bad. It misses both the point - no, bundler has no such comment, but here's a workaround - and the context - this answer was written before bundle outdated or any similar commands were around.

– yfeldblum
Sep 5 '15 at 20:20

add a comment |

I was looking specifically for how to only show the outdated gems that are in my gemfile. Looks like this does it: bundle outdated --only-explicit

That will 'Only list gems specified in your Gemfile, not their dependencies'

Source: https://bundler.io/man/bundle-outdated.1.html

Hopefully this is helpful for someone else.

answered Jan 4 at 0:00

Chnikki

60117

add a comment |

I was looking specifically for how to only show the outdated gems that are in my gemfile. Looks like this does it: bundle outdated --only-explicit

That will 'Only list gems specified in your Gemfile, not their dependencies'

Source: https://bundler.io/man/bundle-outdated.1.html

Hopefully this is helpful for someone else.

answered Jan 4 at 0:00

Chnikki

60117

add a comment |

I was looking specifically for how to only show the outdated gems that are in my gemfile. Looks like this does it: bundle outdated --only-explicit

That will 'Only list gems specified in your Gemfile, not their dependencies'

Source: https://bundler.io/man/bundle-outdated.1.html

Hopefully this is helpful for someone else.

answered Jan 4 at 0:00

Chnikki

60117

I was looking specifically for how to only show the outdated gems that are in my gemfile. Looks like this does it: bundle outdated --only-explicit

That will 'Only list gems specified in your Gemfile, not their dependencies'

Source: https://bundler.io/man/bundle-outdated.1.html

Hopefully this is helpful for someone else.

answered Jan 4 at 0:00

Chnikki

60117

answered Jan 4 at 0:00

Chnikki

60117

answered Jan 4 at 0:00

Chnikki

60117

answered Jan 4 at 0:00

Chnikki

60117

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Bdtjtk