Release automation ~broken about fillertext

@colindean I think that the actions require just an email, and a name, so it shouldn't matter. Here is some sort of explanation with respect to Vagrant, but this should translate well here as well.

I've seen many gem tutorials mention about creating a version.rb file seperately, as is given in this example. So we create a new version file inside lib, I guess? Because if you check the conventional version.rb, the insides are:

# frozen_string_literal: true

module Foodie
  VERSION = "0.1.0"
end

[colindean]

Can you see what juwelier expects?

I may also just... abandon juwelier if it's getting in the way here.

Juwelier hasn't been maintained for some time, and maybe there are alternatives to publishing gems, so we can look into that?

[colindean]

It might be time to drop it then.

It might be time to drop it then.

I think that it might be better to generate a project from Bundler with the same name, and then transfer all the libraries. I can open a new branch, and start with this task.

[colindean]

Have at it!

@colindean you might want to create a new branch called migrate_to_bundler, so that you can merge my PR, and test it out....

@colindean can you check out the migrate_from_juwlier branch in my repo ? The test cases need to be worked on, which I'll fix in my spare time.

[colindean]

Message ID: ***@***.***>Yeah, I might have some time this weekend.

[colindean]

#41 is done and this is building now. If the release publishes correctly, it's done!

Looks like the latest version v.0.3.2 is failing, because of a Rubocop offense, which is quite easy to fix. Simply typing in rubocop --auto-correct would fix the offense.

[colindean]

Thank you for your help, @Ashvith!

[colindean]

https://rubygems.org/gems/fillertext/versions/0.3.4