You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vault gem uses the aws-sigv4 gem in the gemspec and has not been locked.
Yesterday, the vault gem started failing in Ruby 2.3 when the aws-eventstream and aws-sigv4 gems were upgraded to 1.3.0 and 1.7.0 respectively.
Although, the README says that Vault is still is supported in Ruby versions >2.0.0. The release of aws gems used as dependencies are breaking the vault in EOL Ruby environments.
Locking the aws-sigv4 version to the earliest available versions also won't help because the aws-eventstream lock was introduced as '~> 1.0', '>= 1.0.2')here which still points to the latest version and eventually breaks on Ruby 2.3.
The solution is to lock, aws-sigv4 to 1.6.0 and aws-eventstream to 1.2.0 for Ruby versions < 2.4.0 in the vault.gemspec.
The text was updated successfully, but these errors were encountered:
The vault gem uses the aws-sigv4 gem in the gemspec and has not been locked.
Yesterday, the vault gem started failing in Ruby 2.3 when the aws-eventstream and aws-sigv4 gems were upgraded to 1.3.0 and 1.7.0 respectively.
Although, the README says that Vault is still is supported in Ruby versions >2.0.0. The release of aws gems used as dependencies are breaking the vault in EOL Ruby environments.
Locking the aws-sigv4 version to the earliest available versions also won't help because the aws-eventstream lock was introduced as
'~> 1.0', '>= 1.0.2')
here which still points to the latest version and eventually breaks on Ruby 2.3.The solution is to lock, aws-sigv4 to 1.6.0 and aws-eventstream to 1.2.0 for Ruby versions < 2.4.0 in the vault.gemspec.
The text was updated successfully, but these errors were encountered: