Bump figaro from 0.7.0 to 1.1.1 #2871
Conversation
![dependabot-preview[bot]](https://avatars.githubusercontent.com/in/2141?s=60&v=4){kind=small}
Bumps [figaro](https://github.com/laserlemon/figaro) from 0.7.0 to 1.1.1. - [Release notes](https://github.com/laserlemon/figaro/releases) - [Changelog](https://github.com/laserlemon/figaro/blob/master/CHANGELOG.md) - [Commits](laserlemon/figaro@v0.7.0...v1.1.1) Signed-off-by: dependabot[bot] <[email protected]>
| @@ -846,6 +844,7 @@ DEPENDENCIES | |||
| uglifier (>= 1.0.3) | |||
| unicorn | |||
| unicorn-rails | |||
| web! | |||
There was a problem hiding this comment.
Bundler, why are u doing this?
There was a problem hiding this comment.
that web is the engine...
There was a problem hiding this comment.
I explain this here:
#2735 (comment)
There was a problem hiding this comment.
I know, it's just that it's moving it up and down the file...
There was a problem hiding this comment.
it's putting it in the right place (alphabetical order), I edited the gemfile.lock myself (renamed the engine)! that's what it is correcting.
There was a problem hiding this comment.
so the move is from the alphabetical order position of "content" (previous name) to "web" (new name)
There was a problem hiding this comment.
Cool. This whole dependabot thing makes me understand which gems are actually doing what in our code base. :-)
I had a look at https://github.com/laserlemon/figaro#how-do-i-upgrade-to-figaro-10 which mentions breaking changes. But since we don't use Figaro.env and we don't use the Rake task, we are fine. Everything should work as before.
|
Anything to test on this one? |
|
Just a sanity check. If the application.yml can't be loaded properly, the application crashes. |
|
Sally just tested. All good. Merging. |
Bumps figaro from 0.7.0 to 1.1.1.
Changelog
Sourced from figaro's changelog.
Commits
d97fb63Target version 1.1.1fb000e4Add a missing changelog entry7e9d34bMerge pull request #191 from feature/no-crash-on-empty-blocksba95740add a spec for the empty-env config1bab1ccallow empty environment configuration7d950c1Target version 1.1.0619b47aMerge pull request #177 from fny/heroku-remote-flag-support2d5f693Upgrade to Travis' Docker infrastructure5fde2a7Build against Ruby 2.231e14a8Build against Rails 4.2 stable rather than betaDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking
Bump nowin your Dependabot dashboard.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge@dependabot reopenwill reopen this PR if it is closed@dependabot ignore this [patch|minor|major] versionwill close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard:
Finally, you can contact us by mentioning @dependabot.