gitlab-grape-openapi 0.1.1 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8f0408d05e90c29d726e2992e29455b1244d6dc028a28c9e63be8c1d4cfc1a23
-  data.tar.gz: 10157f62f24d46cb7e768fb141fdf391db6015d342f72f766b4225faa53919df
+  metadata.gz: afbabc9163e59aafb950577da68e96bd817c5c4357e2eae88aabe4b75baaaf1f
+  data.tar.gz: 74a9b9a8abb13c4a122bf59169dd7aaa147162f68b781b47d729c52bd8440f50
 SHA512:
-  metadata.gz: feb73a721b4d65eb5078105c4c21d360a86aeb93538164d115bf358fc38dadea00b5e2c177b23d2e5adc5cbae5c6172306c0ca4bb78a78a5a0a27f7154ef9f80
-  data.tar.gz: d61316ee6a5e1c20ae95e9f35430cff097d3b484301d2622ac426ee4355382b992dac5ae71db0dd492acf1f41eaa50b421b6d2bc86b52a99fd3af04f68cbc0b5
+  metadata.gz: c9af1518142acff74821ed05d46605c9f6e33b8f08ccc33d438324196467dc573d6661b48d5b9b247d362b8b864ce0909755d8952d3e1b302b077bfa03aa6b7f
+  data.tar.gz: 03161ba25486070010a7ec67f2955a42f5d82e46c0eb78dbb4065f5df49870b69d9927a78afa40b513c04e9075806005eb558354cf59f4db10946928001a6cb1

data/README.md

@@ -266,6 +266,58 @@ merge:
 The first rule is the one that publishes: a `push` to the default
 branch that changes `lib/**/version.rb`.
 
+#### Verifying changes against `gitlab-org/gitlab`
+
+Because the monorepo consumes this gem from RubyGems, a change can pass
+this gem's own specs locally yet still break `gitlab-org/gitlab` CI once
+the published gem is pulled in. Verify both locally and in CI before
+releasing.
+
+**Locally**, point the monorepo's `Gemfile` at your working copy of this
+gem with a `path:` override:
+
+```ruby
+gem 'gitlab-grape-openapi', path: '<absolute path to this repo>', feature_category: :api
+```
+
+Run `bundle install` in the monorepo, then exercise the affected paths
+(for example regenerate the spec with `bin/rake gitlab:openapi:v3:generate`
+and run the relevant specs). When finished, revert with
+`git restore Gemfile Gemfile.lock` so the override does not leak into a
+commit.
+
+**In CI**, a `path:` override only sees your local checkout, so open a
+throwaway merge request in `gitlab-org/gitlab` that pins the `Gemfile` to
+the exact commit you want to test and let its pipeline run. Replace the
+dependency line:
+
+```ruby
+gem 'gitlab-grape-openapi', '~> <CURRENT_VERSION>', feature_category: :api
+```
+
+with a Git source:
+
+```ruby
+gem 'gitlab-grape-openapi',
+  git: 'https://gitlab.com/gitlab-org/ruby/gems/gitlab-grape-openapi.git',
+  ref: '<commit SHA>',
+  feature_category: :api
+```
+
+Pinning with `ref:` (rather than `branch:`) freezes the exact commit so
+CI does not drift if the branch moves. `Gemfile.next` is a symlink to
+`Gemfile`, so this single edit covers both. Run `bundle install` to
+regenerate `Gemfile.lock` with a GIT source block, commit it (do not
+hand-edit it), and push. To faithfully reproduce the real migration's CI
+conditions, also remove the in-tree gem under `gems/gitlab-grape-openapi/`
+and its `.gitlab/ci/gitlab-gems.gitlab-ci.yml` and `.gitlab/CODEOWNERS`
+entries, so Bundler cannot fall back to the vendored copy.
+
+This throwaway branch is verification-only — do not merge it. Once the
+gem is published, the real version bump uses a `'~> <NEW_VERSION>'`
+constraint instead of the Git source (see the post-release steps in
+`CLAUDE.md`).
+
 ## Contributing
 
 This gem is maintained by GitLab's API Platform team for internal use.

data/lib/gitlab/grape_openapi/version.rb

@@ -2,6 +2,6 @@
 
 module Gitlab
   module GrapeOpenapi
-    VERSION = "0.1.1"
+    VERSION = "0.2.0"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-grape-openapi
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.2.0
 platform: ruby
 authors:
 - group::api
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-06-04 00:00:00.000000000 Z
+date: 2026-06-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: grape
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.0.0
+        version: '2.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 2.0.0
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: grape-entity
   requirement: !ruby/object:Gem::Requirement