cybrid_api_id_ruby 0.129.1073 → 0.129.1076

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (74) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +4 -4
  3. data/README.md +5 -5
  4. data/cybrid_api_id_ruby.gemspec +1 -1
  5. data/lib/cybrid_api_id_ruby/api/bank_applications_idp_api.rb +1 -1
  6. data/lib/cybrid_api_id_ruby/api/customer_tokens_idp_api.rb +1 -1
  7. data/lib/cybrid_api_id_ruby/api/organization_applications_idp_api.rb +1 -1
  8. data/lib/cybrid_api_id_ruby/api/users_idp_api.rb +1 -1
  9. data/lib/cybrid_api_id_ruby/api_client.rb +1 -1
  10. data/lib/cybrid_api_id_ruby/api_error.rb +1 -1
  11. data/lib/cybrid_api_id_ruby/configuration.rb +1 -1
  12. data/lib/cybrid_api_id_ruby/models/application_idp_model.rb +1 -1
  13. data/lib/cybrid_api_id_ruby/models/application_list_idp_model.rb +1 -1
  14. data/lib/cybrid_api_id_ruby/models/application_with_secret_all_of_idp_model.rb +1 -1
  15. data/lib/cybrid_api_id_ruby/models/application_with_secret_idp_model.rb +1 -1
  16. data/lib/cybrid_api_id_ruby/models/customer_token_idp_model.rb +1 -1
  17. data/lib/cybrid_api_id_ruby/models/error_response_idp_model.rb +1 -1
  18. data/lib/cybrid_api_id_ruby/models/patch_application_idp_model.rb +1 -1
  19. data/lib/cybrid_api_id_ruby/models/patch_user_idp_model.rb +1 -1
  20. data/lib/cybrid_api_id_ruby/models/post_bank_application_idp_model.rb +1 -1
  21. data/lib/cybrid_api_id_ruby/models/post_customer_token_idp_model.rb +1 -1
  22. data/lib/cybrid_api_id_ruby/models/post_organization_application_idp_model.rb +1 -1
  23. data/lib/cybrid_api_id_ruby/models/post_user_idp_model.rb +1 -1
  24. data/lib/cybrid_api_id_ruby/models/user_idp_model.rb +1 -1
  25. data/lib/cybrid_api_id_ruby/models/user_list_idp_model.rb +1 -1
  26. data/lib/cybrid_api_id_ruby/version.rb +2 -2
  27. data/lib/cybrid_api_id_ruby.rb +1 -1
  28. data/spec/api/bank_applications_idp_api_spec.rb +1 -1
  29. data/spec/api/customer_tokens_idp_api_spec.rb +1 -1
  30. data/spec/api/organization_applications_idp_api_spec.rb +1 -1
  31. data/spec/api/users_idp_api_spec.rb +1 -1
  32. data/spec/api_client_spec.rb +1 -1
  33. data/spec/configuration_spec.rb +1 -1
  34. data/spec/models/application_idp_model_spec.rb +1 -1
  35. data/spec/models/application_list_idp_model_spec.rb +1 -1
  36. data/spec/models/application_with_secret_all_of_idp_model_spec.rb +1 -1
  37. data/spec/models/application_with_secret_idp_model_spec.rb +1 -1
  38. data/spec/models/customer_token_idp_model_spec.rb +1 -1
  39. data/spec/models/error_response_idp_model_spec.rb +1 -1
  40. data/spec/models/patch_application_idp_model_spec.rb +1 -1
  41. data/spec/models/patch_user_idp_model_spec.rb +1 -1
  42. data/spec/models/post_bank_application_idp_model_spec.rb +1 -1
  43. data/spec/models/post_customer_token_idp_model_spec.rb +1 -1
  44. data/spec/models/post_organization_application_idp_model_spec.rb +1 -1
  45. data/spec/models/post_user_idp_model_spec.rb +1 -1
  46. data/spec/models/user_idp_model_spec.rb +1 -1
  47. data/spec/models/user_list_idp_model_spec.rb +1 -1
  48. data/spec/spec_helper.rb +1 -1
  49. data/vendor/bundle/ruby/4.0.0/cache/io-console-0.9.3.gem +0 -0
  50. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/byebug-13.0.0/gem_make.out +5 -5
  51. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/date-3.5.1/gem_make.out +5 -5
  52. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/{io-console-0.9.2 → io-console-0.9.3}/gem_make.out +19 -18
  53. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/io-console-0.9.3/io/console.so +0 -0
  54. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/{io-console-0.9.2 → io-console-0.9.3}/mkmf.log +4 -0
  55. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  56. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/psych-5.5.0/gem_make.out +5 -5
  57. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/racc-1.8.1/gem_make.out +5 -5
  58. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/stringio-3.2.0/gem_make.out +5 -5
  59. data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/ext/io/console/Makefile +2 -2
  60. data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/ext/io/console/console.c +98 -13
  61. data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/ext/io/console/extconf.rb +15 -1
  62. data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/lib/io/console/size.rb +4 -2
  63. data/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/lib/io/console.so +0 -0
  64. data/vendor/bundle/ruby/4.0.0/specifications/{io-console-0.9.2.gemspec → io-console-0.9.3.gemspec} +3 -3
  65. metadata +17 -17
  66. data/vendor/bundle/ruby/4.0.0/cache/io-console-0.9.2.gem +0 -0
  67. data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/io-console-0.9.2/io/console.so +0 -0
  68. data/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/lib/io/console.so +0 -0
  69. /data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/{io-console-0.9.2 → io-console-0.9.3}/gem.build_complete +0 -0
  70. /data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/.document +0 -0
  71. /data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/BSDL +0 -0
  72. /data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/COPYING +0 -0
  73. /data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/README.md +0 -0
  74. /data/vendor/bundle/ruby/4.0.0/gems/{io-console-0.9.2 → io-console-0.9.3}/ext/io/console/win32_vk.inc +0 -0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read bank_applications:write bank_applications:execute accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read organization_applications:write organization_applications:execute banks:read banks:write banks:execute bank_applications:read bank_applications:write bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.129.1073
6
+ The version of the OpenAPI document: v0.129.1076
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read bank_applications:write bank_applications:execute accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read organization_applications:write organization_applications:execute banks:read banks:write banks:execute bank_applications:read bank_applications:write bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.129.1073
6
+ The version of the OpenAPI document: v0.129.1076
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/spec/spec_helper.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read bank_applications:write bank_applications:execute accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read organization_applications:write organization_applications:execute banks:read banks:write banks:execute bank_applications:read bank_applications:write bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.129.1073
6
+ The version of the OpenAPI document: v0.129.1076
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
6
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-94t0r3 sitelibdir\=./.gem.20260911-3683-94t0r3 clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-ca0k52 sitelibdir\=./.gem.20260914-3670-ca0k52 clean
7
7
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
8
8
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
9
9
 
10
10
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
11
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-94t0r3 sitelibdir\=./.gem.20260911-3683-94t0r3
11
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-ca0k52 sitelibdir\=./.gem.20260914-3670-ca0k52
12
12
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
13
13
  compiling breakpoint.c
14
14
  compiling byebug.c
@@ -39,12 +39,12 @@ linking shared-object byebug/byebug.so
39
39
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
40
40
 
41
41
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
42
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-94t0r3 sitelibdir\=./.gem.20260911-3683-94t0r3 install
42
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-ca0k52 sitelibdir\=./.gem.20260914-3670-ca0k52 install
43
43
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
44
- /usr/bin/install -c -m 0755 byebug.so ./.gem.20260911-3683-94t0r3/byebug
44
+ /usr/bin/install -c -m 0755 byebug.so ./.gem.20260914-3670-ca0k52/byebug
45
45
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
46
46
 
47
47
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
48
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-94t0r3 sitelibdir\=./.gem.20260911-3683-94t0r3 clean
48
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-ca0k52 sitelibdir\=./.gem.20260914-3670-ca0k52 clean
49
49
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
50
50
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
@@ -6,12 +6,12 @@ checking for altzone in time.h with -Werror... no
6
6
  creating Makefile
7
7
 
8
8
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
9
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-vmpn7y sitelibdir\=./.gem.20260911-3683-vmpn7y clean
9
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-6v8c2y sitelibdir\=./.gem.20260914-3670-6v8c2y clean
10
10
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
11
11
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
12
12
 
13
13
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
14
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-vmpn7y sitelibdir\=./.gem.20260911-3683-vmpn7y
14
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-6v8c2y sitelibdir\=./.gem.20260914-3670-6v8c2y
15
15
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
16
16
  compiling date_core.c
17
17
  compiling date_parse.c
@@ -21,12 +21,12 @@ linking shared-object date_core.so
21
21
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
22
22
 
23
23
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
24
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-vmpn7y sitelibdir\=./.gem.20260911-3683-vmpn7y install
24
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-6v8c2y sitelibdir\=./.gem.20260914-3670-6v8c2y install
25
25
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
26
- /usr/bin/install -c -m 0755 date_core.so ./.gem.20260911-3683-vmpn7y
26
+ /usr/bin/install -c -m 0755 date_core.so ./.gem.20260914-3670-6v8c2y
27
27
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
28
28
 
29
29
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
30
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-vmpn7y sitelibdir\=./.gem.20260911-3683-vmpn7y clean
30
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-6v8c2y sitelibdir\=./.gem.20260914-3670-6v8c2y clean
31
31
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
32
32
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
@@ -1,4 +1,4 @@
1
- current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console
1
+ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console
2
2
  /usr/local/bin/ruby extconf.rb
3
3
  checking for rb_interned_str_cstr()... yes
4
4
  checking for rb_ractor_local_storage_value_newkey()... yes
@@ -14,27 +14,28 @@ checking for rb_category_warn()... yes
14
14
  checking for RB_WARN_CATEGORY_DEPRECATED... yes
15
15
  checking for ttyname_r()... yes
16
16
  checking for rb_prepend_module()... yes
17
+ checking for gperf... no
17
18
  creating Makefile
18
19
 
19
- current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console
20
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-o699gn sitelibdir\=./.gem.20260911-3683-o699gn clean
21
- make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
22
- make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
20
+ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console
21
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-kqwl5 sitelibdir\=./.gem.20260914-3670-kqwl5 clean
22
+ make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
23
+ make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
23
24
 
24
- current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console
25
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-o699gn sitelibdir\=./.gem.20260911-3683-o699gn
26
- make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
25
+ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console
26
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-kqwl5 sitelibdir\=./.gem.20260914-3670-kqwl5
27
+ make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
27
28
  compiling console.c
28
29
  linking shared-object io/console.so
29
- make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
30
+ make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
30
31
 
31
- current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console
32
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-o699gn sitelibdir\=./.gem.20260911-3683-o699gn install
33
- make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
34
- /usr/bin/install -c -m 0755 console.so ./.gem.20260911-3683-o699gn/io
35
- make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
32
+ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console
33
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-kqwl5 sitelibdir\=./.gem.20260914-3670-kqwl5 install
34
+ make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
35
+ /usr/bin/install -c -m 0755 console.so ./.gem.20260914-3670-kqwl5/io
36
+ make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
36
37
 
37
- current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console
38
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-o699gn sitelibdir\=./.gem.20260911-3683-o699gn clean
39
- make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
40
- make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.2/ext/io/console'
38
+ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console
39
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-kqwl5 sitelibdir\=./.gem.20260914-3670-kqwl5 clean
40
+ make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
41
+ make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.3/ext/io/console'
@@ -353,3 +353,7 @@ checked program was:
353
353
 
354
354
  --------------------
355
355
 
356
+ find_executable: checking for gperf... -------------------- no
357
+
358
+ --------------------
359
+
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
6
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-fht1jz sitelibdir\=./.gem.20260911-3683-fht1jz clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-bgp0fn sitelibdir\=./.gem.20260914-3670-bgp0fn clean
7
7
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
8
8
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
9
9
 
10
10
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
11
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-fht1jz sitelibdir\=./.gem.20260911-3683-fht1jz
11
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-bgp0fn sitelibdir\=./.gem.20260914-3670-bgp0fn
12
12
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
13
13
  compiling adj_matrix.c
14
14
  adj_matrix.c: In function ‘adj_matrix_default’:
@@ -26,12 +26,12 @@ linking shared-object jaro_winkler/jaro_winkler_ext.so
26
26
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
27
27
 
28
28
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
29
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-fht1jz sitelibdir\=./.gem.20260911-3683-fht1jz install
29
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-bgp0fn sitelibdir\=./.gem.20260914-3670-bgp0fn install
30
30
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
31
- /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20260911-3683-fht1jz/jaro_winkler
31
+ /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20260914-3670-bgp0fn/jaro_winkler
32
32
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
33
33
 
34
34
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
35
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-fht1jz sitelibdir\=./.gem.20260911-3683-fht1jz clean
35
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-bgp0fn sitelibdir\=./.gem.20260914-3670-bgp0fn clean
36
36
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
37
37
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
@@ -4,7 +4,7 @@ checking for pkg-config for yaml-0.1... [" ", "", "-lyaml"]
4
4
  creating Makefile
5
5
 
6
6
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
7
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-bzj2ur sitelibdir\=./.gem.20260911-3683-bzj2ur clean
7
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-swih86 sitelibdir\=./.gem.20260914-3670-swih86 clean
8
8
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
9
9
  cd libyaml && make clean
10
10
  /bin/sh: 1: cd: can't cd to libyaml
@@ -12,7 +12,7 @@ make[1]: [Makefile:287: clean-so] Error 2 (ignored)
12
12
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
13
13
 
14
14
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
15
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-bzj2ur sitelibdir\=./.gem.20260911-3683-bzj2ur
15
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-swih86 sitelibdir\=./.gem.20260914-3670-swih86
16
16
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
17
17
  compiling psych.c
18
18
  compiling psych_emitter.c
@@ -23,13 +23,13 @@ linking shared-object psych.so
23
23
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
24
24
 
25
25
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
26
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-bzj2ur sitelibdir\=./.gem.20260911-3683-bzj2ur install
26
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-swih86 sitelibdir\=./.gem.20260914-3670-swih86 install
27
27
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
28
- /usr/bin/install -c -m 0755 psych.so ./.gem.20260911-3683-bzj2ur
28
+ /usr/bin/install -c -m 0755 psych.so ./.gem.20260914-3670-swih86
29
29
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
30
30
 
31
31
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
32
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-bzj2ur sitelibdir\=./.gem.20260911-3683-bzj2ur clean
32
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-swih86 sitelibdir\=./.gem.20260914-3670-swih86 clean
33
33
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
34
34
  cd libyaml && make clean
35
35
  /bin/sh: 1: cd: can't cd to libyaml
@@ -3,24 +3,24 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
6
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-1zdeuh sitelibdir\=./.gem.20260911-3683-1zdeuh clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-zweihu sitelibdir\=./.gem.20260914-3670-zweihu clean
7
7
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
8
8
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
9
9
 
10
10
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
11
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-1zdeuh sitelibdir\=./.gem.20260911-3683-1zdeuh
11
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-zweihu sitelibdir\=./.gem.20260914-3670-zweihu
12
12
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
13
13
  compiling cparse.c
14
14
  linking shared-object racc/cparse.so
15
15
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
16
16
 
17
17
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
18
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-1zdeuh sitelibdir\=./.gem.20260911-3683-1zdeuh install
18
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-zweihu sitelibdir\=./.gem.20260914-3670-zweihu install
19
19
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
20
- /usr/bin/install -c -m 0755 cparse.so ./.gem.20260911-3683-1zdeuh/racc
20
+ /usr/bin/install -c -m 0755 cparse.so ./.gem.20260914-3670-zweihu/racc
21
21
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
22
22
 
23
23
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
24
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-1zdeuh sitelibdir\=./.gem.20260911-3683-1zdeuh clean
24
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-zweihu sitelibdir\=./.gem.20260914-3670-zweihu clean
25
25
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
26
26
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
@@ -4,24 +4,24 @@ checking for rb_io_mode_t in ruby/io.h... yes
4
4
  creating Makefile
5
5
 
6
6
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
7
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-dg3hbv sitelibdir\=./.gem.20260911-3683-dg3hbv clean
7
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-rvlx2g sitelibdir\=./.gem.20260914-3670-rvlx2g clean
8
8
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
9
9
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
10
10
 
11
11
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
12
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-dg3hbv sitelibdir\=./.gem.20260911-3683-dg3hbv
12
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-rvlx2g sitelibdir\=./.gem.20260914-3670-rvlx2g
13
13
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
14
14
  compiling stringio.c
15
15
  linking shared-object stringio.so
16
16
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
17
17
 
18
18
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
19
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-dg3hbv sitelibdir\=./.gem.20260911-3683-dg3hbv install
19
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-rvlx2g sitelibdir\=./.gem.20260914-3670-rvlx2g install
20
20
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
21
- /usr/bin/install -c -m 0755 stringio.so ./.gem.20260911-3683-dg3hbv
21
+ /usr/bin/install -c -m 0755 stringio.so ./.gem.20260914-3670-rvlx2g
22
22
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
23
23
 
24
24
  current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
25
- make DESTDIR\= sitearchdir\=./.gem.20260911-3683-dg3hbv sitelibdir\=./.gem.20260911-3683-dg3hbv clean
25
+ make DESTDIR\= sitearchdir\=./.gem.20260914-3670-rvlx2g sitelibdir\=./.gem.20260914-3670-rvlx2g clean
26
26
  make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
27
27
  make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
@@ -167,8 +167,8 @@ TARGET_SO = $(TARGET_SO_DIR)$(DLLIB)
167
167
  CLEANLIBS = $(TARGET_SO)
168
168
  CLEANOBJS = $(OBJS) *.bak
169
169
  TARGET_SO_DIR_TIMESTAMP = $(TIMESTAMP_DIR)/.sitearchdir.-.io.time
170
-
171
- VK_HEADER =
170
+ ###
171
+ all: # the default target
172
172
 
173
173
  all: $(DLLIB)
174
174
  static: $(STATIC_LIB)