luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/website/Gemfile.lock

162 lines
3.8 KiB
Plaintext
Raw Normal View History

update middleman version
2017-06-06 20:00:11 +00:00
GEM
remote: https://rubygems.org/
specs:
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
activesupport (4.2.11.1)
update middleman version
2017-06-06 20:00:11 +00:00
i18n (~> 0.7)
minitest (~> 5.1)
thread_safe (~> 0.3, >= 0.3.4)
tzinfo (~> 1.1)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
autoprefixer-rails (9.7.4)
update middleman version
2017-06-06 20:00:11 +00:00
execjs
website: fix gemfile.lock (#5429)
2019-03-05 19:55:04 +00:00
bootstrap-sass (3.4.1)
update middleman version
2017-06-06 20:00:11 +00:00
autoprefixer-rails (>= 5.2.1)
website: fix gemfile.lock (#5429)
2019-03-05 19:55:04 +00:00
sassc (>= 2.0.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
builder (3.2.4)
update middleman version
2017-06-06 20:00:11 +00:00
capybara (2.4.4)
mime-types (>= 1.16)
nokogiri (>= 1.3.3)
rack (>= 1.0.0)
rack-test (>= 0.5.4)
xpath (~> 2.0)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
chunky_png (1.3.11)
update middleman version
2017-06-06 20:00:11 +00:00
coffee-script (2.4.1)
coffee-script-source
execjs
coffee-script-source (1.12.2)
compass (1.0.3)
chunky_png (~> 1.2)
compass-core (~> 1.0.2)
compass-import-once (~> 1.0.5)
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
sass (>= 3.3.13, < 3.5)
compass-core (1.0.3)
multi_json (~> 1.0)
sass (>= 3.3.0, < 3.5)
compass-import-once (1.0.5)
sass (>= 3.2, < 3.5)
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
erubis (2.7.0)
bump eventmachine to 1.2.7 in Gemfile.lock (#6389)
2019-08-27 06:00:43 +00:00
eventmachine (1.2.7)
update middleman version
2017-06-06 20:00:11 +00:00
execjs (2.7.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
ffi (1.12.2)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
haml (5.1.2)
update middleman version
2017-06-06 20:00:11 +00:00
temple (>= 0.8.0)
tilt
hike (1.2.3)
hooks (0.4.1)
uber (~> 0.0.14)
http_parser.rb (0.6.0)
i18n (0.7.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
json (2.3.0)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
kramdown (1.17.0)
update middleman version
2017-06-06 20:00:11 +00:00
listen (3.0.8)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
middleman (3.4.1)
coffee-script (~> 2.2)
compass (>= 1.0.0, < 2.0.0)
compass-import-once (= 1.0.5)
execjs (~> 2.0)
haml (>= 4.0.5)
kramdown (~> 1.2)
middleman-core (= 3.4.1)
middleman-sprockets (>= 3.1.2)
sass (>= 3.4.0, < 4.0)
uglifier (~> 2.5)
middleman-core (3.4.1)
activesupport (~> 4.1)
bundler (~> 1.1)
capybara (~> 2.4.4)
erubis
hooks (~> 0.3)
i18n (~> 0.7.0)
listen (~> 3.0.3)
padrino-helpers (~> 0.12.3)
rack (>= 1.4.5, < 2.0)
thor (>= 0.15.2, < 2.0)
tilt (~> 1.4.1, < 2.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
middleman-hashicorp (0.3.43)
website: fix gemfile.lock (#5429)
2019-03-05 19:55:04 +00:00
bootstrap-sass (~> 3.3)
switch analytics from ga to segment
2018-03-08 20:21:18 +00:00
builder (~> 3.2)
middleman (~> 3.4)
middleman-livereload (~> 3.4)
middleman-syntax (~> 3.0)
redcarpet (~> 3.3)
turbolinks (~> 5.0)
update middleman version
2017-06-06 20:00:11 +00:00
middleman-livereload (3.4.6)
em-websocket (~> 0.5.1)
middleman-core (>= 3.3)
rack-livereload (~> 0.3.15)
middleman-sprockets (3.5.0)
middleman-core (>= 3.3)
sprockets (~> 2.12.1)
sprockets-helpers (~> 1.1.0)
sprockets-sass (~> 1.3.0)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
middleman-syntax (3.2.0)
update middleman version
2017-06-06 20:00:11 +00:00
middleman-core (>= 3.2)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
rouge (~> 3.2)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
mime-types (3.3.1)
update middleman version
2017-06-06 20:00:11 +00:00
mime-types-data (~> 3.2015)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
mime-types-data (3.2019.1009)
website: update nokogiri (#5252)
2019-01-22 20:49:16 +00:00
mini_portile2 (2.4.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
minitest (5.14.0)
multi_json (1.14.1)
nokogiri (1.10.7)
website: update nokogiri (#5252)
2019-01-22 20:49:16 +00:00
mini_portile2 (~> 2.4.0)
update to latest middleman-hashicorp this includes minor text fixes for the universal nav
2018-03-06 21:19:36 +00:00
padrino-helpers (0.12.9)
update middleman version
2017-06-06 20:00:11 +00:00
i18n (~> 0.6, >= 0.6.7)
update to latest middleman-hashicorp this includes minor text fixes for the universal nav
2018-03-06 21:19:36 +00:00
padrino-support (= 0.12.9)
tilt (>= 1.4.1, < 3)
padrino-support (0.12.9)
update middleman version
2017-06-06 20:00:11 +00:00
activesupport (>= 3.1)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
rack (1.6.12)
switch analytics from ga to segment
2018-03-08 20:21:18 +00:00
rack-livereload (0.3.17)
update middleman version
2017-06-06 20:00:11 +00:00
rack
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
rack-test (1.1.0)
Bumps to latest middleman-hashicorp version.
2018-01-24 17:32:17 +00:00
rack (>= 1.0, < 3)
update to latest middleman-hashicorp this includes minor text fixes for the universal nav
2018-03-06 21:19:36 +00:00
rb-fsevent (0.10.3)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
rb-inotify (0.10.1)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
ffi (~> 1.0)
redcarpet (3.5.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
rouge (3.15.0)
Bumps to latest middleman-hashicorp version.
2018-01-24 17:32:17 +00:00
sass (3.4.25)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
sassc (2.2.1)
website: fix gemfile.lock (#5429)
2019-03-05 19:55:04 +00:00
ffi (~> 1.9)
website: update sprockets and ffi to dodge CVEs (#4781) * Update sprockets to dodge CVE-2018-3760 and CVE-2014-7819 * update ffi to dodge CVE-2018-1000201
2018-10-19 12:14:01 +00:00
sprockets (2.12.5)
update middleman version
2017-06-06 20:00:11 +00:00
hike (~> 1.2)
multi_json (~> 1.0)
rack (~> 1.0)
tilt (~> 1.1, != 1.3.0)
sprockets-helpers (1.1.0)
sprockets (~> 2.0)
sprockets-sass (1.3.1)
sprockets (~> 2.0)
tilt (~> 1.1)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
temple (0.8.2)
thor (1.0.1)
update middleman version
2017-06-06 20:00:11 +00:00
thread_safe (0.3.6)
tilt (1.4.1)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
turbolinks (5.2.1)
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
turbolinks-source (~> 5.2)
turbolinks-source (5.2.0)
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
tzinfo (1.2.6)
update middleman version
2017-06-06 20:00:11 +00:00
thread_safe (~> 0.1)
uber (0.0.15)
uglifier (2.7.2)
execjs (>= 0.3.0)
json (>= 1.8.0)
xpath (2.1.0)
nokogiri (~> 1.3)
PLATFORMS
ruby
DEPENDENCIES
website: bump middleman version (#7254)
2020-02-11 09:59:14 +00:00
middleman-hashicorp (= 0.3.43)
update middleman version
2017-06-06 20:00:11 +00:00
BUNDLED WITH
website: Update middleman-hashicorp container and Gemfile.lock (#6374) * website: Update middleman-hashicorp container and Gemfile.lock Time marches on, and so do security vulnerabilities in Nokogiri. So it's time for a new container. As with last time, here's a reminder for the next person who needs to update this: - You shouldn't just update the dependency in Gemfile.lock, because your build times will go to heck as you compile Nokogiri from source on every run. So you need an updated container with all the dependencies. - To update the container, you need to push a new tag to the middleman-hashicorp repo. Teamcity does the rest, and will ship a new container to Docker Hub (unless its credentials are out of date, in which case go ask team-eng-serv.) - Once that's pushed: - Update Makefile - Update the Gemfile - Delete Gemfile.lock - `make website` until it comes up, then ctrl-C - Commit the changes * website: Specify a different json version in Gemfile.lock The Consul website uses different containers for preview and deploy, and this oddball JSON version was causing issues. This commit sacrifices a little bit of preview startup speed for (hopefully) working deploys.
2019-08-27 15:05:18 +00:00
1.17.3