Can you release 1.0.0.pre to rubygems?

[ncri]

Would be helpful for using in an engine. We need to create our own copy of the gem and push it to rubygems otherwise. This is because engines don't allow using gems from github.

[seanlinsley]

Could you go into more detail about what you're trying to accomplish?

There is a 1.0.0 milestone set up, that's due in February. Around that time I'll create a beta release, but for now you can just reference Github:

gem 'activeadmin', github: 'gregbell/active_admin'

[ncri]

No, i cannot do

gem 'activeadmin', github: 'gregbell/active_admin'

in an engine. In engines gems are listed in the gemspec file wich doesn not allow references to github:

 s.add_dependency 'activeadmin', '1.0.1.pre'

wouldn't work, as that version is only on github.

[seanlinsley]

You can set up a dependency on 1.0.0:

s.add_dependency 'activeadmin', '~> 1.0.0.pre'

But in the projects that load your gem, you'll have to tell Bundler how to resolve that dependency:

gem 'activeadmin', github: 'gregbell/active_admin'

[ncri]

Ah, well, we want to have the dependency only in the engine, as our app is modular. Putting it in the host app would defeat the point... We would have that dependency in there even if our admin module is not used.

[ncri]

Is there a reason for not pushing a .pre version to ruby gems?

[seanlinsley]

I guess there isn't. Let me update the changelog, and I'll post a release to Rubygems tonight.

[ncri]

Thanks!

[seanlinsley]

@ncri Can you point me to the gem you're building?

@shekibobo (ref: #2640) I'm not sure what to do about the versioning scheme. Ideally we'd be able to tell what version of AA someone is using (that is: release code vs Github code) simply by looking at the version they report when opening a support request. If I release 1.0.0.pre on Rubygems, what does master become?

If instead I release the current master as 1.0.0.rc1 or 1.0.0.beta1, then what would master become?

[ncri]

@seanlinsley: its not public. But anyway, i had pushed an older version of your gem here, which we can reference fine from the engine: http://rubygems.org/gems/yousty-activeadmin

So we are actually fine with this solution. We just need to keep updating it ourselves until there is no official version on rubygems, which is a bit inconvenient.

[shekibobo]

Might just be able to do what bundler does And whenever we release, we bump the version in master afterward.

[shekibobo]

Tag the release, bundle it and push it to rubygems, then bump the version on master.

[sriv]

I am looking forward to this as well, for similar reasons. Rolling out a Gem, which depends on active_admin for all its awesomeness, and adds a bit of it's own features. Any updates on when I could pull the dependency off rubygems?

[seanlinsley]

The only remaining major change that may make it into the 1.0.0 release is #3862, which is a deep refactor of our CSS. If anyone would like to give that a try in their apps and go over the points needed in the as-of-yet unwritten migration guide (#3536), that would help get 1.0.0 out faster.