vagrant-vsphere 1.13.4 → 1.13.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 122ef76e1e318918c3ae41a9d08dd3294a5622778d64d92dc7f9ca5a9a781afc
-  data.tar.gz: 9023bbcf8d47bb0490afaf4669836a9eec929a321e7da1aa8dbd3503fa2011f8
+  metadata.gz: aa08d8d6114c99130e7734b30a121ce7974b405927ad2ae1dfdf7b5df75c0e7a
+  data.tar.gz: fad32b2024c114ef16cd30372cdee7056d785c1ea3886cbff64f9f11c259166f
 SHA512:
-  metadata.gz: 69bfa799b9ebc91c983cb28d021584135b61e56a5d9fed1e77afbb518baa7a34d5132a3eea79c6896119c8c37204496f7924c95c06bef621d982cabd32985bb7
-  data.tar.gz: cdaea22e2995e7ab9cb3cd971f9a5e4225735cc32a5b67b98a0f5280c56596e0744539b599763c5af0644a0000711c7b00fdf1c0120d99fbe779b284817f983f
+  metadata.gz: cd46b2452ec25e62735b21deee3489bafff11f8624f50dfeba604b4b1254401d9aeed2833402838f058e8a33e287a8f2bfc87f9eab1b27106cc7f6c65b262913
+  data.tar.gz: ee875addfb3c573036b7be6bd2621162bb2701009071f4392e5203fc1bbca78fb4271556e149cf07c33feb1c5973efdbe5408f8379a34cf92d12e060de7b9410

data/.bumpversion.cfg

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

data/CHANGELOG.md

@@ -1,3 +1,8 @@
+## [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.

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.4**
+**version: 1.13.5**
 
-vagrant-vsphere (**version: 1.13.4**) 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.4'
+    VERSION = '1.13.5'
   end
 end

data/vSphere.gemspec

@@ -11,8 +11,8 @@ 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'
 
   s.add_dependency 'rbvmomi', '>=1.11.5', '<2.0.0'
 

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-vsphere
 version: !ruby/object:Gem::Version
-  version: 1.13.4
+  version: 1.13.5
 platform: ruby
 authors:
 - Andrew Grauch
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-03-31 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
@@ -197,7 +197,7 @@ homepage: ''
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -213,7 +213,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.0.8
-signing_key: 
+signing_key:
 specification_version: 4
 summary: VMWare vSphere provider
 test_files: