superset 0.5.0 → 0.5.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 59ab63d9f8d51f73e9ca6606a0a559c75def26e9c69ab09eeeb59fd91cf24447
-  data.tar.gz: c7ae83dfa2a5b5f0e100d6cce0d38e7badf04e20d174c661207223493179f851
+  metadata.gz: 063136fe3a4d039c48ce40c5cf060f212af35a3833c6d24ce9315f5465931c5d
+  data.tar.gz: 4310dc351ea932247d997ac2c2a48078c900ca7023845a1859140e4372d1cd8c
 SHA512:
-  metadata.gz: 9f0f70518ea7bc2f9e19ba9c115bdb1c2c44f05abc0e887fcfb0de1934499847841e601ec0d5e8aabb957c368196873cad0bae6ccb300ce55fe8d9eedd3c4e29
-  data.tar.gz: 3a90c54aca065f2187bf971912dc2993f25034f6c1880fb4d973a90da3b2a1d63188871acfe64d7448abd431f27a2ea52ecc91d1c9c55194f9815016b8872b61
+  metadata.gz: e21a7c945bfc292fe86e444b65c14c90dc6a2090554dfe3e2a9a01dd7810a4e3dcaf05aaee39a958523a2343797277163ebcc60d6ff1e3e1e6933fd0355e4a2b
+  data.tar.gz: ad56b23990af5c6823c098bcc4798bcb0dff1e2d2a02ee3f41bdec46e7ca637bf57811d0dcee2938ded9ef55c1efc5fd44cda860c9feb649f2cd39db5c941dd4

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 ## Changelog
 
+## 0.5.2 - 2026-08-28
+
+* Add tag-triggered release workflow (`.github/workflows/release.yml`) that publishes to RubyGems.org via OIDC trusted publishing and to GitHub Packages via the Actions `GITHUB_TOKEN` — no long-lived credentials stored anywhere. Refuses to publish unless the pushed tag's commit is reachable from `develop`. See `RELEASING.md` for the release steps and one-time RubyGems.org Trusted Publisher setup
+* Loosen the `faraday` dependency from `~> 1.10` to `>= 1.10` so consumers aren't held back from newer Faraday releases
+
+## 0.5.1 - 2026-08-27
+
+* **Fix:** `Superset::Client` and `Superset::GuestToken` raised `NameError: uninitialized constant FaradayMiddleware::ParseJson` on every request. Both connections used `FaradayMiddleware::ParseJson`, but this gem has never declared or required `faraday_middleware` — the constant only reached the bundle transitively via happi, and happi 1.0.0 dropped it. Replaced with Faraday's own `f.response :json`, which is equivalent (same `content_type:` option, same `respond_to?(:to_str)` guard, same `Faraday::ParsingError` on bad bodies)
+* Raise the `faraday` floor from `~> 1.0` to `~> 1.10` — `Faraday::Response::Json` only ships from 1.10
+* Pin the development `happi` to v1.0.0 so `faraday_middleware` is absent from this gem's own bundle and CI catches any reintroduction
+* Add `#connection` specs to both classes asserting the handler stack, which the previous suite never exercised
+
 ## 0.5.0 - 2026-07-21
 
 * Decouple from Rollbar — remove the `Rollbar.error(...) if defined?(Rollbar)` call in `WarmUpCache`; exceptions now propagate to the caller so consumers' own error handling can react

data/RELEASING.md

@@ -0,0 +1,32 @@
+# Releasing superset
+
+Publishing is only ever done by GitHub Actions (`.github/workflows/release.yml`), triggered by
+a `vX.Y.Z` tag whose commit is reachable from `develop`. Tags on any other branch are rejected by
+the workflow before anything is built. No one needs local publishing credentials — the workflow
+authenticates to RubyGems.org via OIDC trusted publishing and to GitHub Packages via the
+Actions-provided `GITHUB_TOKEN`.
+
+## Cutting a release
+
+1. Bump `Superset::VERSION` in `lib/superset/version.rb`.
+2. Add a new `## X.Y.Z - YYYY-MM-DD` entry to the top of `CHANGELOG.md` describing the changes.
+3. Commit both changes and get them onto `develop` (PR + merge, as normal).
+4. From an up-to-date `develop`, tag the commit and push the tag:
+
+   ```bash
+   git tag vX.Y.Z
+   git push origin vX.Y.Z
+   ```
+
+5. Watch the "Release" workflow run in the Actions tab.
+6. Confirm the new version shows up on [rubygems.org](https://rubygems.org/gems/superset) and on
+   [GitHub Packages](https://github.com/rdytech/superset-client/pkgs/rubygems/superset).
+
+## One-time setup
+
+- **RubyGems.org**: an existing owner of the `superset` gem must add a Trusted Publisher for
+  `rdytech/superset-client`, workflow `release.yml` (no environment). See
+  [Trusted Publishing: adding a publisher](https://guides.rubygems.org/trusted-publishing/adding-a-publisher/).
+  Until this is done, the "Publish to RubyGems.org" step will fail.
+- **GitHub Packages**: nothing to configure — the workflow's `packages: write` permission is
+  sufficient.

data/lib/superset/client.rb

@@ -77,7 +77,7 @@ module Superset
       @connection ||= Faraday.new(superset_host) do |f|
         f.authorization :Bearer, access_token
         f.use :cookie_jar  # persist the Flask session cookie across the csrf_token GET and the write
-        f.use FaradayMiddleware::ParseJson, content_type: 'application/json'
+        f.response :json, content_type: 'application/json'
 
         if self.config.use_json
           f.request :json

data/lib/superset/guest_token.rb

@@ -75,7 +75,7 @@ module Superset
       @connection ||= Faraday.new(authenticator.superset_host) do |f|
         f.authorization :Bearer, access_token
         f.use :cookie_jar  # replay the Flask session cookie from the csrf_token GET on the POST
-        f.use FaradayMiddleware::ParseJson, content_type: 'application/json'
+        f.response :json, content_type: 'application/json'
         f.request :json
         f.adapter :net_http
       end

data/lib/superset/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Superset
-  VERSION = "0.5.0"
+  VERSION = "0.5.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: superset
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.2
 platform: ruby
 authors:
 - jbat
@@ -55,16 +55,16 @@ dependencies:
   name: faraday
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '1.10'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.0'
+        version: '1.10'
 - !ruby/object:Gem::Dependency
   name: faraday-multipart
   requirement: !ruby/object:Gem::Requirement
@@ -207,6 +207,7 @@ files:
 - Dockerfile
 - LICENSE
 - README.md
+- RELEASING.md
 - Rakefile
 - doc/duplicate_dashboards.md
 - doc/migrating_dashboards_across_environments.md
@@ -290,7 +291,6 @@ files:
 - lib/superset/tag/list.rb
 - lib/superset/version.rb
 - log/README.md
-- superset.gemspec
 homepage: https://github.com/rdytech/superset-client
 licenses:
 - MIT
@@ -309,7 +309,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.7
+rubygems_version: 3.6.9
 specification_version: 4
 summary: A Ruby Client for Apache Superset API
 test_files: []

data/superset.gemspec

@@ -1,59 +0,0 @@
-# frozen_string_literal: true
-
-require_relative "lib/superset/version"
-
-Gem::Specification.new do |spec|
-  spec.name = "superset"
-  spec.version = Superset::VERSION
-  spec.authors = ["jbat"]
-  spec.email = ["jonathon.batson@gmail.com"]
-
-  spec.summary = "A Ruby Client for Apache Superset API"
-  spec.homepage = "https://github.com/rdytech/superset-client"
-  spec.license = "MIT"
-  spec.required_ruby_version = ">= 3"
-
-  #spec.metadata["allowed_push_host"] = ""
-
-  #spec.metadata["homepage_uri"] = spec.homepage
-  #spec.metadata["source_code_uri"] = ""
-  #spec.metadata["changelog_uri"] = ""
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files = Dir.chdir(__dir__) do
-    `git ls-files -z`.split("\x0").reject do |f|
-      (File.expand_path(f) == __FILE__) ||
-        f.start_with?(*%w[bin/ test/ spec/ features/ .git appveyor Gemfile])
-    end
-  end
-
-  #spec.bindir = "exe"
-  #spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
-  spec.require_paths = [
-    "lib"
-  ]
-
-  spec.add_dependency "json", ">= 2.0"
-  spec.add_dependency "terminal-table", "~> 4.0"
-  spec.add_dependency "require_all", ">= 3.0"
-  spec.add_dependency "faraday", "~> 1.0"
-  spec.add_dependency "faraday-multipart", "~> 1.0"
-  spec.add_dependency "faraday-cookie_jar", "~> 0.0.7"  # replay the Flask session cookie for CSRF
-  spec.add_dependency "enumerate_it", ">= 1.7"
-
-  # rubyzip is only needed by the dashboard import/export feature, which lazily
-  # `require 'zip'` at call time. Kept as a dev dependency so those specs run here,
-  # but NOT a runtime dependency — consumers that don't import/export (embedders,
-  # read/write API clients) shouldn't inherit its rubyzip >= 3 pin.
-  # Apps that DO use import/export must declare rubyzip (>= 3.0) themselves.
-  spec.add_development_dependency "rubyzip", ">= 3.0"
-  spec.add_development_dependency "dotenv", ">= 2.0"
-  spec.add_development_dependency "rake", ">= 13.0"
-  spec.add_development_dependency "rspec", ">= 3.0"
-  spec.add_development_dependency "rubocop", ">= 1.0"
-  spec.add_development_dependency "pry", ">= 0.14"
-
-  # For more information and examples about making a new gem, check out our
-  # guide at: https://bundler.io/guides/creating_gem.html
-end