https://github.com/maxmind/minfraud-api-ruby
Ruby API for minFraud
https://github.com/maxmind/minfraud-api-ruby
maxmind minfraud
Last synced: 10 months ago
JSON representation
Ruby API for minFraud
- Host: GitHub
- URL: https://github.com/maxmind/minfraud-api-ruby
- Owner: maxmind
- License: mit
- Created: 2016-09-26T10:15:21.000Z (over 9 years ago)
- Default Branch: main
- Last Pushed: 2025-08-13T16:27:30.000Z (10 months ago)
- Last Synced: 2025-08-13T18:34:42.747Z (10 months ago)
- Topics: maxmind, minfraud
- Language: Ruby
- Homepage: https://rubygems.org/gems/minfraud
- Size: 494 KB
- Stars: 14
- Watchers: 15
- Forks: 7
- Open Issues: 0
-
Metadata Files:
- Readme: README.dev.md
- Changelog: CHANGELOG.md
- License: LICENSE.txt
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Prereqs
* You must have a local Ruby environment that can run the tests
via `rake`.
* You must have the [GitHub CLI tool (gh)](https://cli.github.com/)
installed, in your path, and logged into an account that can
make GitHub releases on the repo.
* Your environment also must have `bash`, `git`, `perl`, and `sed`
available.
# How to release
* Review open issues and PRs to see if anything needs to be addressed
before release.
* Create a branch e.g. `horgh/release` and switch to it.
* `main` is protected.
* Set the release version and release date in `CHANGELOG.md`. Be sure
the version follows [Semantic Versioning](https://semver.org/).
* Commit these changes.
* Run `dev-bin/release.sh`.
* Verify the release on the GitHub Releases page.
* If everything goes well, the authorized releasers will receive an email
to review the pending deployment. If you are an authorized releaser,
you will need to approve the release deployment run. If you are not,
you will have to wait for an authorized releaser to do so.
* Double check it looks okay at https://rubygems.org/gems/minfraud and
https://www.rubydoc.info/gems/minfraud.
* Make a PR and get it merged.