search

samvera-deprecated / curation_concerns

A Hydra-based Rails Engine that extends an application, adding the ability to Create, Read, Update and Destroy (CRUD) objects (based on Hydra::Works) and providing a generator for defining object types with custom workflows, views, access controls, etc.
Other
15 stars 27 forks source link

bump version to 1.7.8 #1188

Closed jrochkind closed 7 years ago

jrochkind commented 7 years ago

@mjgiarlo, I don't have permissions to actually merge this, perhaps because it's failing travis? Would you mind merging this, trying to release a 1.7.8 that has no differences from 1.7.7 but

If this gets merged, I'll try to actually do a release, find out if I have privileges to do that then I guess.

mjgiarlo commented 7 years ago

@jrochkind HMU if something doesn't work and I can make sure you get all the bits you need.

jrochkind commented 7 years ago

@mjgiarlo I do not have privs to do a rubygems release of curation_concerns. (I seem to recall there was supposed to be some script that gave it to me everywhere? I guess not). 

$ bundle exec rake release
curation_concerns 1.7.8 built to pkg/curation_concerns-1.7.8.gem.
Tagged v1.7.8.
Pushed git commits and tags.
rake aborted!
Pushing gem to https://rubygems.org...
You do not have permission to push to this gem. Ask an owner to add you with: gem owner curation_concerns --add jonathan@dnil.net
mjgiarlo commented 7 years ago

@jrochkind Can you add a PR that adds your GitHub username and Rubygems.org email address to this hash? https://github.com/samvera/hydra/blob/master/script/grant_revoke_gem_authority.rb#L23-L58

jrochkind commented 7 years ago

I could swear I already did that once, but apparently not! Or maybe I'm getting confused and thought someone told me after filling out the legal form I was supposed to be automatically added everywhere just by that. Anyway, ok, sure, tomorrow.