okay 12.0.0 → 12.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d440392d2c9d86cd93c694b618d46f18935339c70897e5b6869a8b556ed17953
-  data.tar.gz: 63cb6c74cacfa7985707ae8bae9213b680ec5b097c184d588199ed7b7f5d6a21
+  metadata.gz: 8d00ba14dec86133bf583190685d2df4145dad9bcc741b9934a6f1deed7efdbc
+  data.tar.gz: 9f2997054914a1df28dbc968f3d0d7f950253b572dfbc9e7981d0c4847e61978
 SHA512:
-  metadata.gz: f45cc9fe3188a53c2492459b1e4c614ab0d7400a0b891a5b1324304b0d34c5650e9a6f048c71427c770bc7205fd283f167e537244efd31df299454445ddfb477
-  data.tar.gz: e6d44d3186e410d8e9f95050534c4e1f13f7c86a53d6b0e4eb6197d0e3e053ba7184251166d21495b537b86bde07ea757fc37d0f246950f4027a734a103467c8
+  metadata.gz: 2bc3352be68702f3dda8c9c214103c75bbd39b4def0592d0b5797c744e1b18f7bf9ae0975aa267cf4b7c49415536f3e23b55a9a76c99537995bc2af717be0d8a
+  data.tar.gz: 1460955b26d90c22373590a5a6573e5696c5ca8d023a1403f532b60729d48d14d44a1608bf4c761bff482d12c400b7bb9d64bc8c09d8b434c1aea4755f368b12

data/lib/okay/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Okay
-  VERSION = "12.0.0"
+  VERSION = "12.0.1"
 end

data/okay.gemspec

@@ -16,8 +16,8 @@ Gem::Specification.new do |spec|
   spec.homepage      = "https://github.com/duckinator/okay"
   spec.license       = "MIT"
 
-  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
-    f.match(%r{^(test|spec|features)/})
+  spec.files         = `git ls-files -z`.split("\x0").select do |f|
+    f.match(%r{^(README.md|LICENSE.txt|okay.gemspec|lib)})
   end
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: okay
 version: !ruby/object:Gem::Version
-  version: 12.0.0
+  version: 12.0.1
 platform: ruby
 authors:
 - Ellen Marie Dash
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-08-13 00:00:00.000000000 Z
+date: 2021-09-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cacert
@@ -74,21 +74,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".cirrus.yml"
-- ".gitignore"
-- ".rspec"
-- CODE_OF_CONDUCT.md
-- Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
-- Rakefile
-- bin/console
-- bin/httpbin
-- bin/setup
-- bors.toml
-- examples/github-graphql-example.rb
-- examples/github-graphql-intentional-failure-example.rb
 - lib/okay.rb
 - lib/okay/default.rb
 - lib/okay/graphql.rb
@@ -117,7 +104,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.15
+rubygems_version: 3.3.0.dev
 signing_key:
 specification_version: 4
 summary: Okay, minimalist implementations of common utilities.

data/.cirrus.yml

@@ -1,23 +0,0 @@
-# Allow compute credits usage by collaborators and bors.
-use_compute_credits: $CIRRUS_USER_COLLABORATOR == 'true' || $CIRRUS_BRANCH == 'master' || $CIRRUS_BRANCH == 'staging' || $CIRRUS_BRANCH == 'trying'
-
-Linux_task:
-  container:
-    matrix:
-      - image: ruby:2.6-slim
-      - image: ruby:2.7-slim
-      - image: ruby:3.0-slim
-  install_script:
-    # git is installed since the gemspec uses it.
-    - apt-get update && apt-get install -y git
-    - gem install bundler
-    - bundle install
-  script:
-    - ruby --version
-    - bundle exec rake spec
-
-task:
-  name: CI Success
-  container: {image: "busybox"}
-  depends_on:
-    - Linux

data/.gitignore

@@ -1,11 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-
-# rspec failure tracking
-.rspec_status

data/.rspec

@@ -1,2 +0,0 @@
---format documentation
---color

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at me@duckie.co. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,15 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-# Okay only supports Ruby versions under "normal maintenance".
-# This number should be updated when a Ruby version goes into security
-# maintenance.
-#
-# Ruby maintenance info: https://www.ruby-lang.org/en/downloads/branches/
-#
-# NOTE: Update how_is.gemspec when this is updated!
-ruby ">= 2.6"
-
-# Specify your gem's dependencies in okay.gemspec
-gemspec

data/Gemfile.lock

@@ -1,40 +0,0 @@
-PATH
-  remote: .
-  specs:
-    okay (11.0.0)
-      cacert
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    cacert (0.6.0)
-    diff-lcs (1.4.4)
-    rake (12.3.3)
-    rspec (3.10.0)
-      rspec-core (~> 3.10.0)
-      rspec-expectations (~> 3.10.0)
-      rspec-mocks (~> 3.10.0)
-    rspec-core (3.10.1)
-      rspec-support (~> 3.10.0)
-    rspec-expectations (3.10.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.10.0)
-    rspec-mocks (3.10.2)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.10.0)
-    rspec-support (3.10.2)
-
-PLATFORMS
-  x86_64-freebsd-13
-
-DEPENDENCIES
-  bundler (~> 2.0)
-  okay!
-  rake (~> 12.3)
-  rspec (~> 3.8)
-
-RUBY VERSION
-   ruby 3.0.1p64
-
-BUNDLED WITH
-   2.2.15

data/Rakefile

@@ -1,8 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "okay"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/httpbin

@@ -1,3 +0,0 @@
-#!/bin/bash
-
-docker run -p 80:80 kennethreitz/httpbin

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/bors.toml

@@ -1,5 +0,0 @@
-status = ["CI Success"]
-
-# Uncomment this to use a two hour timeout.
-# The default is one hour.
-#timeout_sec = 7200

data/examples/github-graphql-example.rb

@@ -1,11 +0,0 @@
-require "okay/graphql"
-
-query = Okay::GraphQL.query {
-  viewer {
-    login
-  }
-}
-
-headers = { bearer_token: ENV['DEMO_GITHUB_TOKEN'] }
-results = query.submit!(:github, headers).or_raise!
-puts results.from_json

data/examples/github-graphql-intentional-failure-example.rb

@@ -1,11 +0,0 @@
-require "okay/graphql"
-
-query = Okay::GraphQL.query {
-  viewer {
-    login
-  }
-}
-
-headers = { bearer_token: "oh no, invalid bearer token!" }
-results = query.submit!(:github, headers).or_raise!
-puts results.from_json