launchdarkly-server-sdk 6.2.4 → 6.2.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 326e10ac69bf7d73c5727c555a2981b7d271d1651d9521b976005d93646a188b
-  data.tar.gz: 608205f6ac545e410aaa9e507180b8ad097ebe1ed23c6dc011b2c522209d9e3f
+  metadata.gz: 8f1b216e5ae2518b79aae9613ecd04b02ed525ea2d25084df805eae7d92cb219
+  data.tar.gz: 317db7e14a292968b245e39e3cd4be33206fd8085c8ebd04be43f1c987434228
 SHA512:
-  metadata.gz: a1b648a1d796ad1b65feffd9ee83fcd3dcb63c3146d513e44173d5cb6da32fd29b993d8b7343957094b801b69da5c0873b458fb568e6d174e4c402e158d129c4
-  data.tar.gz: 433d7761a4386538c25a8db6a0520b7d1e8c7184dcc9967e9770bbf5639e3f0a74476f2a0ef20f50bf53a5c6da4df62aacfd444f5fad5cfb1d64bc73a113374f
+  metadata.gz: 5d9182ccde6530f67df30fd8a238e9b510e89dc235cf76c45140cb6eaa36b8e342a44a98595b8c86f171c8f6f1cc74291f3c2ebf11ac274f2a1e46d64798318c
+  data.tar.gz: 4b54fc711795c06e3bdabb9dd593af8499aa8e8c28eec1f9db508a5a6c5288cd0268b7ce9d324c892425ffcf080f0ad21e78060a74e0186f19998bd40f076943

data/README.md

@@ -10,7 +10,7 @@ LaunchDarkly Server-side SDK for Ruby
 
 LaunchDarkly overview
 -------------------------
-[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/docs/getting-started) using LaunchDarkly today!
+[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
  
 [![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
 
@@ -22,7 +22,7 @@ This version of the LaunchDarkly SDK has a minimum Ruby version of 2.5.0, or 9.2
 Getting started
 -----------
 
-Refer to the [SDK documentation](https://docs.launchdarkly.com/docs/ruby-sdk-reference#section-getting-started) for instructions on getting started with using the SDK.
+Refer to the [SDK documentation](https://docs.launchdarkly.com/sdk/server-side/ruby#getting-started) for instructions on getting started with using the SDK.
 
 Learn more
 -----------
@@ -49,7 +49,7 @@ About LaunchDarkly
     * Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
     * Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
     * Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
-* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
+* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Read [our documentation](https://docs.launchdarkly.com/sdk) for a complete list.
 * Explore LaunchDarkly
     * [launchdarkly.com](https://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
     * [docs.launchdarkly.com](https://docs.launchdarkly.com/  "LaunchDarkly Documentation") for our documentation and SDK reference guides

data/lib/ldclient-rb/config.rb

@@ -110,8 +110,8 @@ module LaunchDarkly
     # Whether to use the LaunchDarkly relay proxy in daemon mode. In this mode, the client does not
     # use polling or streaming to get feature flag updates from the server, but instead reads them
     # from the {#feature_store feature store}, which is assumed to be a database that is populated by
-    # a LaunchDarkly relay proxy. For more information, see ["The relay proxy"](https://docs.launchdarkly.com/v2.0/docs/the-relay-proxy)
-    # and ["Using a persistent feature store"](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+    # a LaunchDarkly relay proxy. For more information, see ["The relay proxy"](https://docs.launchdarkly.com/home/relay-proxy)
+    # and ["Using a persistent data stores"](https://docs.launchdarkly.com/sdk/concepts/data-stores).
     #
     # All other properties related to streaming or polling are ignored if this option is set to true.
     #
@@ -189,7 +189,7 @@ module LaunchDarkly
     # from LaunchDarkly, and uses the last stored data when evaluating flags. Defaults to
     # {InMemoryFeatureStore}; for other implementations, see {LaunchDarkly::Integrations}.
     #
-    # For more information, see ["Using a persistent feature store"](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+    # For more information, see ["Persistent data stores"](https://docs.launchdarkly.com/sdk/concepts/data-stores).
     #
     # @return [LaunchDarkly::Interfaces::FeatureStore]
     #

data/lib/ldclient-rb/integrations/dynamodb.rb

@@ -7,7 +7,7 @@ module LaunchDarkly
       #
       # Creates a DynamoDB-backed persistent feature store. For more details about how and why you can
       # use a persistent feature store, see the
-      # [SDK reference guide](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+      # [SDK reference guide](https://docs.launchdarkly.com/sdk/features/storing-data#ruby).
       #
       # To use this method, you must first install one of the AWS SDK gems: either `aws-sdk-dynamodb`, or
       # the full `aws-sdk`. Then, put the object returned by this method into the `feature_store` property

data/lib/ldclient-rb/integrations/redis.rb

@@ -25,7 +25,7 @@ module LaunchDarkly
       #
       # Creates a Redis-backed persistent feature store. For more details about how and why you can
       # use a persistent feature store, see the
-      # [SDK reference guide](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+      # [SDK reference guide](https://docs.launchdarkly.com/sdk/features/storing-data#rubys).
       #
       # To use this method, you must first have the `redis` and `connection-pool` gems installed. Then,
       # put the object returned by this method into the `feature_store` property of your

data/lib/ldclient-rb/interfaces.rb

@@ -9,7 +9,7 @@ module LaunchDarkly
     # client uses the feature store to persist feature flags and related objects received from
     # the LaunchDarkly service. Implementations must support concurrent access and updates.
     # For more about how feature stores can be used, see:
-    # [Using a persistent feature store](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
+    # [Using a persistent feature store](https://docs.launchdarkly.com/sdk/features/storing-data#ruby).
     #
     # An entity that can be stored in a feature store is a hash that can be converted to and from
     # JSON, and that has at a minimum the following properties: `:key`, a string that is unique

data/lib/ldclient-rb/ldclient.rb

@@ -132,7 +132,7 @@ module LaunchDarkly
 
     #
     # Creates a hash string that can be used by the JavaScript SDK to identify a user.
-    # For more information, see [Secure mode](https://docs.launchdarkly.com/docs/js-sdk-reference#section-secure-mode).
+    # For more information, see [Secure mode](https://docs.launchdarkly.com/sdk/features/secure-mode#ruby).
     #
     # @param user [Hash] the user properties
     # @return [String] a hash string
@@ -172,11 +172,11 @@ module LaunchDarkly
     #
     # Other supported user attributes include IP address, country code, and an arbitrary hash of
     # custom attributes. For more about the supported user properties and how they work in
-    # LaunchDarkly, see [Targeting users](https://docs.launchdarkly.com/docs/targeting-users).
+    # LaunchDarkly, see [Targeting users](https://docs.launchdarkly.com/home/flags/targeting-users).
     # 
     # The optional `:privateAttributeNames` user property allows you to specify a list of
     # attribute names that should not be sent back to LaunchDarkly.
-    # [Private attributes](https://docs.launchdarkly.com/docs/private-user-attributes)
+    # [Private attributes](https://docs.launchdarkly.com/home/users/attributes#creating-private-user-attributes)
     # can also be configured globally in {Config}.
     #
     # @example Basic user hash
@@ -213,7 +213,7 @@ module LaunchDarkly
     # be included in analytics events, if you are capturing detailed event data for this flag.
     #
     # For more information, see the reference guide on
-    # [Evaluation reasons](https://docs.launchdarkly.com/v2.0/docs/evaluation-reasons).
+    # [Evaluation reasons](https://docs.launchdarkly.com/sdk/concepts/evaluation-reasons).
     #
     # @param key [String] the unique feature key for the feature flag, as shown
     #   on the LaunchDarkly dashboard
@@ -260,7 +260,7 @@ module LaunchDarkly
     #
     # As of this version’s release date, the LaunchDarkly service does not support the `metricValue`
     # parameter. As a result, specifying `metricValue` will not yet produce any different behavior
-    # from omitting it. Refer to the [SDK reference guide](https://docs.launchdarkly.com/docs/ruby-sdk-reference#section-track)
+    # from omitting it. Refer to the [SDK reference guide](https://docs.launchdarkly.com/sdk/features/events#ruby)
     # for the latest status.
     #
     # @param event_name [String] The name of the event

data/lib/ldclient-rb/version.rb

@@ -1,3 +1,3 @@
 module LaunchDarkly
-  VERSION = "6.2.4"
+  VERSION = "6.2.5"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: launchdarkly-server-sdk
 version: !ruby/object:Gem::Version
-  version: 6.2.4
+  version: 6.2.5
 platform: ruby
 authors:
 - LaunchDarkly
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-08-11 00:00:00.000000000 Z
+date: 2021-10-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-dynamodb
@@ -198,14 +198,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.1
+        version: 2.1.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.1
+        version: 2.1.1
 - !ruby/object:Gem::Dependency
   name: json
   requirement: !ruby/object:Gem::Requirement
@@ -247,37 +247,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".circleci/config.yml"
-- ".github/ISSUE_TEMPLATE/bug_report.md"
-- ".github/ISSUE_TEMPLATE/config.yml"
-- ".github/ISSUE_TEMPLATE/feature_request.md"
-- ".github/pull_request_template.md"
-- ".gitignore"
-- ".hound.yml"
-- ".ldrelease/build-docs.sh"
-- ".ldrelease/circleci/linux/execute.sh"
-- ".ldrelease/circleci/mac/execute.sh"
-- ".ldrelease/circleci/template/build.sh"
-- ".ldrelease/circleci/template/gems-setup.sh"
-- ".ldrelease/circleci/template/prepare.sh"
-- ".ldrelease/circleci/template/publish.sh"
-- ".ldrelease/circleci/template/test.sh"
-- ".ldrelease/circleci/template/update-version.sh"
-- ".ldrelease/circleci/windows/execute.ps1"
-- ".ldrelease/config.yml"
-- ".rspec"
-- ".rubocop.yml"
-- ".simplecov"
-- CHANGELOG.md
-- CODEOWNERS
-- CONTRIBUTING.md
-- Gemfile
 - LICENSE.txt
 - README.md
-- azure-pipelines.yml
-- docs/Makefile
-- docs/index.md
-- launchdarkly-server-sdk.gemspec
 - lib/launchdarkly-server-sdk.rb
 - lib/ldclient-rb.rb
 - lib/ldclient-rb/cache_store.rb
@@ -322,49 +293,6 @@ files:
 - lib/ldclient-rb/user_filter.rb
 - lib/ldclient-rb/util.rb
 - lib/ldclient-rb/version.rb
-- spec/config_spec.rb
-- spec/diagnostic_events_spec.rb
-- spec/evaluation_detail_spec.rb
-- spec/event_sender_spec.rb
-- spec/event_summarizer_spec.rb
-- spec/events_spec.rb
-- spec/expiring_cache_spec.rb
-- spec/feature_store_spec_base.rb
-- spec/file_data_source_spec.rb
-- spec/fixtures/feature.json
-- spec/fixtures/feature1.json
-- spec/fixtures/user.json
-- spec/flags_state_spec.rb
-- spec/http_util.rb
-- spec/impl/evaluator_bucketing_spec.rb
-- spec/impl/evaluator_clause_spec.rb
-- spec/impl/evaluator_operators_spec.rb
-- spec/impl/evaluator_rule_spec.rb
-- spec/impl/evaluator_segment_spec.rb
-- spec/impl/evaluator_spec.rb
-- spec/impl/evaluator_spec_base.rb
-- spec/impl/event_factory_spec.rb
-- spec/impl/model/serialization_spec.rb
-- spec/in_memory_feature_store_spec.rb
-- spec/integrations/consul_feature_store_spec.rb
-- spec/integrations/dynamodb_feature_store_spec.rb
-- spec/integrations/store_wrapper_spec.rb
-- spec/launchdarkly-server-sdk_spec.rb
-- spec/launchdarkly-server-sdk_spec_autoloadtest.rb
-- spec/ldclient_end_to_end_spec.rb
-- spec/ldclient_spec.rb
-- spec/newrelic_spec.rb
-- spec/polling_spec.rb
-- spec/redis_feature_store_spec.rb
-- spec/requestor_spec.rb
-- spec/segment_store_spec_base.rb
-- spec/simple_lru_cache_spec.rb
-- spec/spec_helper.rb
-- spec/store_spec.rb
-- spec/stream_spec.rb
-- spec/user_filter_spec.rb
-- spec/util_spec.rb
-- spec/version_spec.rb
 homepage: https://github.com/launchdarkly/ruby-server-sdk
 licenses:
 - Apache-2.0
@@ -384,51 +312,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
+rubygems_version: 3.2.29
 signing_key: 
 specification_version: 4
 summary: LaunchDarkly SDK for Ruby
-test_files:
-- spec/config_spec.rb
-- spec/diagnostic_events_spec.rb
-- spec/evaluation_detail_spec.rb
-- spec/event_sender_spec.rb
-- spec/event_summarizer_spec.rb
-- spec/events_spec.rb
-- spec/expiring_cache_spec.rb
-- spec/feature_store_spec_base.rb
-- spec/file_data_source_spec.rb
-- spec/fixtures/feature.json
-- spec/fixtures/feature1.json
-- spec/fixtures/user.json
-- spec/flags_state_spec.rb
-- spec/http_util.rb
-- spec/impl/evaluator_bucketing_spec.rb
-- spec/impl/evaluator_clause_spec.rb
-- spec/impl/evaluator_operators_spec.rb
-- spec/impl/evaluator_rule_spec.rb
-- spec/impl/evaluator_segment_spec.rb
-- spec/impl/evaluator_spec.rb
-- spec/impl/evaluator_spec_base.rb
-- spec/impl/event_factory_spec.rb
-- spec/impl/model/serialization_spec.rb
-- spec/in_memory_feature_store_spec.rb
-- spec/integrations/consul_feature_store_spec.rb
-- spec/integrations/dynamodb_feature_store_spec.rb
-- spec/integrations/store_wrapper_spec.rb
-- spec/launchdarkly-server-sdk_spec.rb
-- spec/launchdarkly-server-sdk_spec_autoloadtest.rb
-- spec/ldclient_end_to_end_spec.rb
-- spec/ldclient_spec.rb
-- spec/newrelic_spec.rb
-- spec/polling_spec.rb
-- spec/redis_feature_store_spec.rb
-- spec/requestor_spec.rb
-- spec/segment_store_spec_base.rb
-- spec/simple_lru_cache_spec.rb
-- spec/spec_helper.rb
-- spec/store_spec.rb
-- spec/stream_spec.rb
-- spec/user_filter_spec.rb
-- spec/util_spec.rb
-- spec/version_spec.rb
+test_files: []

data/.circleci/config.yml

@@ -1,43 +0,0 @@
-# This CircleCI configuration was generated by Releaser for a specific release. It is not to be used
-# for regular CI builds. Be aware that rerunning this build may cause it to repeat release actions
-# such as publishing to a package manager. However, it will not perform any Git actions other than
-# reading the repository.
-version: 2.1
-workflows:
-  test:
-    jobs:
-      - release_linux:
-          context: org-global
-jobs:
-  release_linux:
-    docker:
-      - image: circleci/ruby:2.6.6-buster
-    environment:
-      LD_RELEASE_CIRCLECI_TYPE: linux
-      LD_RELEASE_BRANCH: "master"
-      LD_RELEASE_CIRCLECI_BRANCH: ""
-      LD_RELEASE_DOCS_GITHUB_PAGES: "1"
-      LD_RELEASE_DOCS_TITLE: ""
-      LD_RELEASE_PROJECT: "ruby-server-sdk"
-      LD_RELEASE_PROJECT_TEMPLATE: "ruby"
-      LD_RELEASE_VERSION: "6.2.4"
-      LD_SKIP_DATABASE_TESTS: "1"
-    steps:
-      - checkout
-      - run:
-          name: "Releaser: prepare"
-          command: .ldrelease/circleci/mac/execute.sh prepare .ldrelease/circleci/template/prepare.sh
-      - run:
-          name: "Releaser: build"
-          command: .ldrelease/circleci/mac/execute.sh build .ldrelease/circleci/template/build.sh
-      - run:
-          name: "Releaser: test"
-          command: .ldrelease/circleci/mac/execute.sh test .ldrelease/circleci/template/test.sh
-      - run:
-          name: "Releaser: build-docs"
-          command: .ldrelease/circleci/mac/execute.sh build-docs .ldrelease/build-docs.sh
-      - run:
-          name: "Releaser: publish"
-          command: .ldrelease/circleci/mac/execute.sh publish .ldrelease/circleci/template/publish.sh
-      - store_artifacts:
-          path: artifacts

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,37 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Is this a support request?**
-This issue tracker is maintained by LaunchDarkly SDK developers and is intended for feedback on the SDK code. If you're not sure whether the problem you are having is specifically related to the SDK, or to the LaunchDarkly service overall, it may be more appropriate to contact the LaunchDarkly support team; they can help to investigate the problem and will consult the SDK team if necessary. You can submit a support request by going [here](https://support.launchdarkly.com/hc/en-us/requests/new) or by emailing support@launchdarkly.com.
-
-Note that issues filed on this issue tracker are publicly accessible. Do not provide any private account information on your issues. If your problem is specific to your account, you should submit a support request as described above.
-
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-**To reproduce**
-Steps to reproduce the behavior.
-
-**Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Logs**
-If applicable, add any log output related to your problem.
-
-**SDK version**
-The version of this SDK that you are using.
-
-**Language version, developer tools**
-For instance, Go 1.11 or Ruby 2.5.3. If you are using a language that requires a separate compiler, such as C, please include the name and version of the compiler too.
-
-**OS/platform**
-For instance, Ubuntu 16.04, Windows 10, or Android 4.0.3. If your code is running in a browser, please also include the browser type and version.
-
-**Additional context**
-Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Support request
-    url: https://support.launchdarkly.com/hc/en-us/requests/new
-    about: File your support requests with LaunchDarkly's support team

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I would love to see the SDK [...does something new...]
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context about the feature request here.

data/.github/pull_request_template.md

@@ -1,21 +0,0 @@
-**Requirements**
-
-- [ ] I have added test coverage for new or changed functionality
-- [ ] I have followed the repository's [pull request submission guidelines](../blob/master/CONTRIBUTING.md#submitting-pull-requests)
-- [ ] I have validated my changes against all supported platform versions
-
-**Related issues**
-
-Provide links to any issues in this repository or elsewhere relating to this pull request.
-
-**Describe the solution you've provided**
-
-Provide a clear and concise description of what you expect to happen.
-
-**Describe alternatives you've considered**
-
-Provide a clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-
-Add any other context about the pull request here.

data/.gitignore

@@ -1,16 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/docs/build
-/pkg/
-/spec/reports/
-/tmp/
-*.bundle
-*.so
-*.o
-*.a
-mkmf.log
-*.gem
-.DS_Store
-Gemfile.lock

data/.hound.yml

@@ -1,2 +0,0 @@
-ruby:
-  config_file: .rubocop

data/.ldrelease/build-docs.sh

@@ -1,18 +0,0 @@
-#!/bin/bash
-
-# doc generation is not part of Releaser's standard Ruby project template
-
-mkdir -p ./artifacts/
-
-cd ./docs
-make
-cd ..
-
-# Releaser will pick up docs generated in CI if we put an archive of them in the
-# artifacts directory and name it docs.tar.gz or docs.zip. They will be uploaded
-# to GitHub Pages and also attached as release artifacts. There's no separate
-# "publish-docs" step because the external service that also hosts them doesn't
-# require an upload, it just picks up gems automatically.
-
-cd ./docs/build/html
-tar cfz ../../../artifacts/docs.tar.gz *

data/.ldrelease/circleci/linux/execute.sh

@@ -1,18 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Performs a delegated release step in a CircleCI Linux container. This mechanism is described
-# in scripts/circleci/README.md. All of the necessary environment variables should already be
-# in the generated CircleCI configuration.
-
-mkdir -p artifacts
-
-export LD_RELEASE_TEMP_DIR=/tmp/project-releaser-temp
-mkdir -p ${LD_RELEASE_TEMP_DIR}
-
-STEP="$1"
-SCRIPT="$2"
-echo
-echo "[${STEP}] executing ${SCRIPT}"
-"./${SCRIPT}"

data/.ldrelease/circleci/mac/execute.sh

@@ -1,18 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Performs a delegated release step in a CircleCI Mac container. This mechanism is described
-# in scripts/circleci/README.md. All of the necessary environment variables should already be
-# in the generated CircleCI configuration.
-
-mkdir -p artifacts
-
-export LD_RELEASE_TEMP_DIR=/tmp/project-releaser-temp
-mkdir -p ${LD_RELEASE_TEMP_DIR}
-
-STEP="$1"
-SCRIPT="$2"
-echo
-echo "[${STEP}] executing ${SCRIPT}"
-"./${SCRIPT}"

data/.ldrelease/circleci/template/build.sh

@@ -1,19 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Standard build.sh for Ruby-based projects that publish a gem
-
-echo "Using gem $(gem --version)"
-
-#shellcheck source=/dev/null
-source "$(dirname "$0")/gems-setup.sh"
-
-echo; echo "Installing dependencies"
-${BUNDLER_COMMAND} install
-
-# Build Ruby Gem - this assumes there is a single .gemspec file in the main project directory
-# Note that the gemspec must be able to get the project version either from $LD_RELEASE_VERSION,
-# or from somewhere in the source code that the project-specific update-version.sh has updated.
-echo "Running gem build"
-gem build ./*.gemspec || { echo "gem build failed" >&2; exit 1; }

data/.ldrelease/circleci/template/gems-setup.sh

@@ -1,16 +0,0 @@
-#!/bin/bash
-
-# helper script to set GEM_HOME, PATH, and BUNDLER_COMMAND for Ruby - must be sourced, not executed
-
-mkdir -p "${LD_RELEASE_TEMP_DIR}/gems"
-export GEM_HOME="${LD_RELEASE_TEMP_DIR}/gems"
-export PATH="${GEM_HOME}/bin:${PATH}"
-
-# also, determine whether we'll need to run a specific version of Bundler
-
-GEMSPEC_BUNDLER_VERSION=$(sed -n -e "s/.*['\"]bundler['\"], *['\"]\([^'\"]*\)['\"]/\1/p" ./*.gemspec | tr -d ' ')
-if [ -n "${GEMSPEC_BUNDLER_VERSION}" ]; then
-  BUNDLER_COMMAND="bundler _${GEMSPEC_BUNDLER_VERSION}_"
-else
-  BUNDLER_COMMAND="bundler"
-fi

data/.ldrelease/circleci/template/prepare.sh

@@ -1,17 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-echo "Using gem $(gem --version)"
-
-#shellcheck source=/dev/null
-source "$(dirname "$0")/gems-setup.sh"
-
-# If the gemspec specifies a certain version of bundler, we need to make sure we install that version.
-echo "Installing bundler"
-if [ -n "${GEMSPEC_BUNDLER_VERSION:-}" ]; then
-  GEMSPEC_OPTIONS="-v ${GEMSPEC_BUNDLER_VERSION}"
-else
-  GEMSPEC_OPTIONS=""
-fi
-gem install bundler ${GEMSPEC_OPTIONS} || { echo "installing bundler failed" >&2; exit 1; }

data/.ldrelease/circleci/template/publish.sh

@@ -1,19 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Standard publish.sh for Ruby-based projects - we can assume build.sh has already been run
-
-#shellcheck source=/dev/null
-source "$(dirname "$0")/gems-setup.sh"
-
-# If we're running in CircleCI, the RubyGems credentials will be in an environment
-# variable and should be copied to the variable the gem command expects
-if [ -n "${LD_RELEASE_RUBYGEMS_API_KEY:-}" ]; then
-  export GEM_HOST_API_KEY="${LD_RELEASE_RUBYGEMS_API_KEY}"
-fi
-
-# Since all Releaser builds are clean builds, we can assume that the only .gem file here
-# is the one we just built
-echo "Running gem push"
-gem push ./*.gem || { echo "gem push failed" >&2; exit 1; }

data/.ldrelease/circleci/template/test.sh

@@ -1,10 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Standard test.sh for Ruby-based projects
-
-#shellcheck source=/dev/null
-source "$(dirname "$0")/gems-setup.sh"
-
-${BUNDLER_COMMAND} exec rspec spec

data/.ldrelease/circleci/template/update-version.sh

@@ -1,8 +0,0 @@
-#!/bin/bash
-
-set -ue
-
-# Standard update-version.sh for Ruby-based projects - this will work only if the version string
-# is in a source file under lib/ that has a line like his: VERSION = "2.0.0"
-
-"$(dirname "$0")/../update-version-constant.sh" lib '*.rb'

data/.ldrelease/circleci/windows/execute.ps1

@@ -1,19 +0,0 @@
-param(
-    [string]$step,
-    [string]$script
-)
-
-# Performs a delegated release step in a CircleCI Windows container using PowerShell. This
-# mechanism is described in scripts/circleci/README.md. All of the necessary environment
-# variables should already be in the generated CircleCI configuration.
-
-$ErrorActionPreference = "Stop"
-
-New-Item -Path "./artifacts" -ItemType "directory" -Force | Out-Null
-
-$env:LD_RELEASE_TEMP_DIR = "$env:TEMP\project-releaser-temp"
-New-Item -Path $env:LD_RELEASE_TEMP_DIR -ItemType "directory" -Force | Out-Null
-
-Write-Host
-Write-Host "[$step] executing $script"
-& "./$script"