Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Github packages for private gem registry [IN-181] #1

Merged
merged 1 commit into from
Sep 11, 2022

Conversation

dleeman
Copy link

@dleeman dleeman commented Jul 15, 2022

Just updates the gemspec to target this repo's Github package registry. Version updated to reflect both the update to the gemspec, but also I suppose the earlier update to handle nested hashes/arrays.

Updated gemspec to specify Github RubyGems package registry as allowed
push host and updated gem version to reflect the change
Copy link

@rmCredly rmCredly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good outside of the single question I had.

@@ -12,6 +12,9 @@ Gem::Specification.new do |s|
s.summary = %q{Simple key/secret based authentication for apis}
s.description = %q{Simple key/secret based authentication for apis}


s.metadata['allowed_push_host'] = "https://rubygems.pkg.github.com/YourAcclaim"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main reason is that this repo is public, whereas the others are not. So the impact to our organization if this were accidentally pushed to a public registry is lower. (There's also an already-published version of this gem in RubyGems, which we don't have keys to push to, which makes it very unlikely we'd accidentally push it to the wrong host.)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see. Thanks for pointing that out.

@dleeman dleeman merged commit caf9e81 into master Sep 11, 2022
@dleeman dleeman deleted the feature/IN-181-private-gem-registry branch September 11, 2022 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants