vagrant-vsphere 1.13.1 → 1.13.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: a0d44c2157fc7b333b6c97c8a027386fb8f9db88
-  data.tar.gz: b1ba99bdba7b06d379f61a1ab55639b21491254b
+SHA256:
+  metadata.gz: aa08d8d6114c99130e7734b30a121ce7974b405927ad2ae1dfdf7b5df75c0e7a
+  data.tar.gz: fad32b2024c114ef16cd30372cdee7056d785c1ea3886cbff64f9f11c259166f
 SHA512:
-  metadata.gz: aaced51e239e3d3567de2d783212a6c8e692e0158223cc21c2d15d2d6b6146b1c8feba6fe59270bf70983d4d410f8eb11e23c4c5988c42464d9bf17b04a3f4aa
-  data.tar.gz: 3b48f0aea570b3861ef2c286b4bd3d521d2e7840f1fc32eb8454c4773d3e690cf8da5d46276287779673d75dc64cb8ead6bad74a8dfc79069bbe64fd57de5967
+  metadata.gz: cd46b2452ec25e62735b21deee3489bafff11f8624f50dfeba604b4b1254401d9aeed2833402838f058e8a33e287a8f2bfc87f9eab1b27106cc7f6c65b262913
+  data.tar.gz: ee875addfb3c573036b7be6bd2621162bb2701009071f4392e5203fc1bbca78fb4271556e149cf07c33feb1c5973efdbe5408f8379a34cf92d12e060de7b9410

data/.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.13.1
+current_version = 1.13.5
 tag = true
 commit = true
 

data/.ruby-version

@@ -1 +1 @@
-2.3.5
+2.6.5

data/.travis.yml

@@ -1,11 +1,4 @@
 language: ruby
 cache: bundler
-rvm:
-  - 2.3.5
-
-before_install:
-  - rvm @global do gem uninstall bundler --all --executables
-  - gem uninstall bundler --all --executables
-  - gem install bundler --version '1.15.4'
 
 sudo: false

data/CHANGELOG.md

@@ -1,4 +1,28 @@
-## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.0)
+## [1.13.5 (2021-01-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.5)
+  - Pin nokogiri to 1.10.10. This fixes an issue where vagrant-vsphere failed to install due to 
+    nokogiri requiring Ruby >=2.5.  This is a workaround until the vagrant-nsidc plugin is updated
+    to work with newer versions of vagrant that are bundled with newer versions of Ruby
+
+## [1.13.4 (2020-03-31)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.4)
+
+  - Allow newer versions of i18n.
+    ([jmartin-r7:release-i18n](https://github.com/nsidc/vagrant-vsphere/pull/286))
+  - Updated .ruby-version to 2.6.5
+  - Fix broken tests.
+    ([wwestenbrink:master](https://github.com/nsidc/vagrant-vsphere/pull/283))
+
+## [1.13.3 (2018-12-06)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.3)
+
+  - Update i18n dependency to allow v1.1.1. This fixes an issue with
+    installation with Vagrant 2.2.x
+    ([jarretlavallee:fix/master/il8n_deps](https://github.com/nsidc/vagrant-vsphere/pull/273)).
+
+## [1.13.2 (2017-12-06)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.2)
+
+  - Update rbvmomi dependency to v1.11.5 and greater (but still less than
+    2.0). v1.11.5 fixes the issue introduced in v1.11.4.
+
+## [1.13.1 (2017-12-05)](https://github.com/nsidc/vagrant-vsphere/releases/tag/v1.13.1)
 
   - Update rbvmomi dependency to avoid v1.11.4; something in
     [2725089](https://github.com/vmware/rbvmomi/commit/2725089a08312315c4eb85f13296fc159f50b4d1)

data/DEVELOPMENT.md

@@ -65,3 +65,25 @@ prefers to be run from the official installer rather than through the gem.
 Despite those warning messages, this is the
 [officially recommended](https://docs.vagrantup.com/v2/plugins/development-basics.html)
 method for Vagrant plugin development.
+
+### Releasing
+
+1) Ensure [travis-ci](https://travis-ci.org/github/nsidc/vagrant-vsphere/) build is passing
+2) Ensure `CHANGELOG.md` is up-to-date with the changes to release
+3) Update version in the code, according to [semver](https://semver.org/)
+    * [bumpversion](https://github.com/peritus/bumpversion) can be used; if not,
+      the version needs to be manually updated in `.bumpversion.cfg`,
+      `README.md`, and `lib/vSphere/version.rb` (e.g., as in
+      [`11eced2`](https://github.com/nsidc/vagrant-vsphere/commit/11eced2))
+4) `bundle exec rake build`
+    * builds the plugin to `pkg/vagrant-vsphere-$VERSION.gem`
+    * install to your system vagrant for further testing with `vagrant plugin
+      install ./pkg/vagrant-vsphere-$VERSION.gem`
+5) `bundle exec rake release`
+    * creates the version tag and pushes it to GitHub
+    * pushes the built gem to
+      [RubyGems.org](https://rubygems.org/gems/vagrant-vsphere/)
+6) Update the [Releases page](https://github.com/nsidc/vagrant-vsphere/releases)
+    * the release name should match the version tag (e.g., `v1.2.3`)
+    * the release description can be the same as the `CHANGELOG.md` entry
+    * upload the `.gem` from RubyGems.org as an attached binary for the release

data/Gemfile

@@ -4,7 +4,7 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem 'vagrant', github: 'mitchellh/vagrant'
+  gem 'vagrant', github: 'mitchellh/vagrant', ref: 'v2.2.6'
 end
 
 group :plugins do

data/README.md

@@ -19,9 +19,9 @@ This provider is built on top of the
 * libxml2, libxml2-dev, libxslt, libxslt-dev
 
 ## Current Version
-**version: 1.13.1**
+**version: 1.13.5**
 
-vagrant-vsphere (**version: 1.13.1**) is available from
+vagrant-vsphere (**version: 1.13.5**) is available from
 [RubyGems.org](https://rubygems.org/gems/vagrant-vsphere)
 
 ## Installation

data/lib/vSphere/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module VSphere
-    VERSION = '1.13.1'
+    VERSION = '1.13.5'
   end
 end

data/spec/spec_helper.rb

@@ -91,6 +91,7 @@ RSpec.configure do |config|
                       :data_dir => Pathname.new(''),
                       :id => nil,
                       :id= => nil,
+                      :name => nil,
                       :guest => double('guest', capability: nil)
 
     @env = {

data/vSphere.gemspec

@@ -11,17 +11,12 @@ Gem::Specification.new do |s|
   s.summary = 'VMWare vSphere provider'
   s.description = 'Enables Vagrant to manage machines with VMWare vSphere.'
 
-  # force the use of Nokogiri 1.5.x to prevent conflicts with older versions of zlib
-  s.add_dependency 'nokogiri', '~>1.5'
+  # pin nokogiri to 1.10.10 to get around 1.11.0 requiring ruby >=2.5
+  s.add_dependency 'nokogiri', '1.10.10'
 
-  # force the use of at least rbvmomi 1.8.2 to work around concurrency errors:
-  # https://github.com/nsidc/vagrant-vsphere/issues/139
-  #
-  # rbvmomi v1.11.4 broke cloning VMs at NSIDC, see
-  # https://github.com/vmware/rbvmomi/issues/127
-  s.add_dependency 'rbvmomi', '>=1.8.2', '<1.11.4'
+  s.add_dependency 'rbvmomi', '>=1.11.5', '<2.0.0'
 
-  s.add_dependency 'i18n', '>=0.6.4', '<=0.8.0'
+  s.add_dependency 'i18n', '>=0.6.4'
 
   s.add_development_dependency 'rake', '11.1.2' # pinned to accommodate rubocop 0.32.1
   s.add_development_dependency 'rspec-core'

metadata

@@ -1,49 +1,49 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-vsphere
 version: !ruby/object:Gem::Version
-  version: 1.13.1
+  version: 1.13.5
 platform: ruby
 authors:
 - Andrew Grauch
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2017-12-05 00:00:00.000000000 Z
+date: 2021-01-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: nokogiri
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '1.5'
+        version: 1.10.10
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - '='
       - !ruby/object:Gem::Version
-        version: '1.5'
+        version: 1.10.10
 - !ruby/object:Gem::Dependency
   name: rbvmomi
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.2
+        version: 1.11.5
     - - "<"
       - !ruby/object:Gem::Version
-        version: 1.11.4
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.8.2
+        version: 1.11.5
     - - "<"
       - !ruby/object:Gem::Version
-        version: 1.11.4
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: i18n
   requirement: !ruby/object:Gem::Requirement
@@ -51,9 +51,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 0.6.4
-    - - "<="
-      - !ruby/object:Gem::Version
-        version: 0.8.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -61,9 +58,6 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 0.6.4
-    - - "<="
-      - !ruby/object:Gem::Version
-        version: 0.8.0
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -203,7 +197,7 @@ homepage: ''
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -218,9 +212,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.5.2.1
-signing_key: 
+rubygems_version: 3.0.8
+signing_key:
 specification_version: 4
 summary: VMWare vSphere provider
 test_files: