Cleanup Repository files and Gem build #536
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KyFaSt
reviewed
Dec 13, 2024
| @@ -1 +0,0 @@ | |||
| 3.1.1 | |||
Contributor
Author
There was a problem hiding this comment.
No particular reason I suppose, although I was thinking that having this locked the version to a very specific version only in development. Since we intend to support this library for at least Ruby 2.6-3.2, I figured it'd be better to unlock the development version. Not strongly opinonated though
Contributor
Author
There was a problem hiding this comment.
I've re-added the file so the Ruby version is pinned in dev
KyFaSt
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates this repository to remove extraneous files, update the README.md, and remove files from the Gem build.
Closes #531
All PRs:
Adding a new header
Generally, adding a new header is always OK.
Adding a new CSP directive