Skip to content

Bump chartkick from 4.2.1 to 5.1.4 #2286

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Bump chartkick from 4.2.1 to 5.1.4 #2286

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Gemfile
View file
Original file line number Diff line number Diff line change
@@ -38,7 +38,7 @@ gem 'bootstrap-social-rails', '~> 4.12'
gem 'bootstrap_form', '~> 2.7'
gem 'bundler' # Ensure it's available
# Note: if webpacker is used, see chartkick website for added instructions
gem 'chartkick', '~> 4.0' # Chart project_stats
gem 'chartkick', '~> 5.1' # Chart project_stats
gem 'faraday-retry', '~> 2.1' # Force retry of faraday requests for reliability
# We no longger use "fastly-rails"; it doesn't support Rails 6+.
# They recommend switching to the "fastly" gem (aka "fastly-ruby"),
4 changes: 2 additions & 2 deletions Gemfile.lock
View file
Original file line number Diff line number Diff line change
@@ -117,7 +117,7 @@ GEM
xpath (~> 3.2)
capybara-slow_finder_errors (0.1.5)
capybara (~> 3.0)
chartkick (4.2.1)
chartkick (5.1.4)
chef-utils (18.6.2)
concurrent-ruby
code_analyzer (0.5.5)
@@ -600,7 +600,7 @@ DEPENDENCIES
bundler
bundler-audit
capybara-slow_finder_errors
chartkick (~> 4.0)
chartkick (~> 5.1)
codecov
dotenv-rails (~> 2.7)
eslintrb

Unchanged files with check annotations Beta

View file
docs/assurance-case.md
as text instead.
In our SACM diagrams we've sometimes omitted the bigdot when there is a
single connection from one element to antoher.

Check failure on line 3424 in docs/assurance-case.md

GitHub Actions / Check for spelling errors 

antoher ==> another
This is not strictly compliant.
One advantage of using “bigdot” even in these
cases would be that it would make it much easier to add