launchdarkly-server-sdk-otel 1.1.1 → 1.1.2

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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 47853aa2256d84af7ea5a245d259e8233b2f788edbbac18afeacb023f427307b
4
- data.tar.gz: ec42f78af2e55ad64e8ead806d49f04d021977ebd36b0540627526d16f3d2425
3
+ metadata.gz: fec2b48bdca2958b0049e343905f479741aa191f200eab72a3c0fa54767dc444
4
+ data.tar.gz: 80bcd06df3797502b1a21268ab4cf3d31e20e85d2b5d69949ea5675db6ffcd52
5
5
  SHA512:
6
- metadata.gz: 2c9abbba443c3d06face161aeca0bc5c4cc1eb070658739956dbcf7d007ec879866ca35016417f601db2cd1c3d63141db9e8e66f9f12948fd712fa68a0f7124c
7
- data.tar.gz: 10e760cb62429725207d77bbe6f35ab30fb8dd68203c94b9794b287227f91d212681756fa6edb8474ebecca45b2a5aa7dbb10153e746fc757d7949db1ac32156
6
+ metadata.gz: fc267ba931e252cd737b6dbe6ef5e96210936795283273f570c4d3b98a5242c85a2a3756bb0f5d132d8296e2fce07978ea882f659db3b8ddd77337ff9633d25e
7
+ data.tar.gz: 7889606131e5ae9834cbe6b29168183cdaad227ded276622ea25d5482c91817d5bcb4fd17bcc6b7886dcfbc01f2b360d320b1ce32e435cd97ae080c47dc3f0ff
@@ -1,3 +1,3 @@
1
1
  {
2
- ".": "1.1.1"
2
+ ".": "1.1.2"
3
3
  }
data/CHANGELOG.md CHANGED
@@ -1,5 +1,12 @@
1
1
  # Changelog
2
2
 
3
+ ## [1.1.2](https://github.com/launchdarkly/ruby-server-sdk-otel/compare/1.1.1...1.1.2) (2026-06-04)
4
+
5
+
6
+ ### Bug Fixes
7
+
8
+ * Loosen launchdarkly-server-sdk constraint to ~> 8.4 ([#25](https://github.com/launchdarkly/ruby-server-sdk-otel/issues/25)) ([160c165](https://github.com/launchdarkly/ruby-server-sdk-otel/commit/160c165d928b87ada6fcc53614953ede6054884f))
9
+
3
10
  ## [1.1.1](https://github.com/launchdarkly/ruby-server-sdk-otel/compare/1.1.0...1.1.1) (2025-10-29)
4
11
 
5
12
 
data/PROVENANCE.md CHANGED
@@ -1,15 +1,15 @@
1
- ## Verifying SDK build provenance with the SLSA framework
1
+ ## Verifying SDK build provenance with GitHub artifact attestations
2
2
 
3
- LaunchDarkly uses the [SLSA framework](https://slsa.dev/spec/v1.0/about) (Supply-chain Levels for Software Artifacts) to help developers make their supply chain more secure by ensuring the authenticity and build integrity of our published SDK packages.
3
+ LaunchDarkly uses [GitHub artifact attestations](https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds) to help developers make their supply chain more secure by ensuring the authenticity and build integrity of our published SDK packages.
4
4
 
5
- As part of [SLSA requirements for level 3 compliance](https://slsa.dev/spec/v1.0/requirements), LaunchDarkly publishes provenance about our SDK package builds using [GitHub's generic SLSA3 provenance generator](https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#generation-of-slsa3-provenance-for-arbitrary-projects) for distribution alongside our packages. These attestations are available for download from the GitHub release page for the release version under Assets > `multiple-provenance.intoto.jsonl`.
5
+ LaunchDarkly publishes provenance about our SDK package builds using [GitHub's `actions/attest` action](https://github.com/actions/attest). These attestations are stored in GitHub's attestation API and can be verified using the [GitHub CLI](https://cli.github.com/).
6
6
 
7
- To verify SLSA provenance attestations, we recommend using [slsa-verifier](https://github.com/slsa-framework/slsa-verifier). Example usage for verifying SDK packages is included below:
7
+ To verify build provenance attestations, we recommend using the [GitHub CLI `attestation verify` command](https://cli.github.com/manual/gh_attestation_verify). Example usage for verifying SDK packages is included below:
8
8
 
9
9
  <!-- x-release-please-start-version -->
10
10
  ```
11
- # Set the version of the SDK to verify
12
- VERSION=1.1.1
11
+ # Set the version of the library to verify
12
+ VERSION=1.1.2
13
13
  ```
14
14
  <!-- x-release-please-end -->
15
15
 
@@ -17,27 +17,33 @@ VERSION=1.1.1
17
17
  # Download gem
18
18
  $ gem fetch launchdarkly-server-sdk-otel -v $VERSION
19
19
 
20
- # Download provenance from Github release
21
- $ curl --location -O \
22
- https://github.com/launchdarkly/ruby-server-sdk-otel/releases/download/${VERSION}/launchdarkly-server-sdk-otel-${VERSION}.gem.intoto.jsonl
23
-
24
- # Run slsa-verifier to verify provenance against package artifacts
25
- $ slsa-verifier verify-artifact \
26
- --provenance-path launchdarkly-server-sdk-otel-${VERSION}.gem.intoto.jsonl \
27
- --source-uri github.com/launchdarkly/ruby-server-sdk-otel \
28
- launchdarkly-server-sdk-otel-${VERSION}.gem
20
+ # Verify provenance using the GitHub CLI
21
+ $ gh attestation verify launchdarkly-server-sdk-otel-${VERSION}.gem --owner launchdarkly
29
22
  ```
30
23
 
31
24
  Below is a sample of expected output.
32
25
 
33
26
  ```
34
- Verified signature against tlog entry index 83653185 at URL: https://rekor.sigstore.dev/api/v1/log/entries/24296fb24b8ad77a7df0bbf87a7d5fcaafa551a2101d9f993d251a56a918bb113e81d2c575dc7e25
35
- Verified build using builder "https://github.com/slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@refs/tags/v1.10.0" at commit 14c48a68c45871c27409591969e7f4c0ebdcdf62
36
- Verifying artifact launchdarkly-server-sdk-otel-1.0.0.gem: PASSED
27
+ Loaded digest sha256:... for file://launchdarkly-server-sdk-otel-1.1.1.gem
28
+ Loaded 1 attestation from GitHub API
29
+
30
+ The following policy criteria will be enforced:
31
+ - Predicate type must match:................ https://slsa.dev/provenance/v1
32
+ - Source Repository Owner URI must match:... https://github.com/launchdarkly
33
+ - Subject Alternative Name must match regex: (?i)^https://github.com/launchdarkly/
34
+ - OIDC Issuer must match:................... https://token.actions.githubusercontent.com
35
+
36
+ ✓ Verification succeeded!
37
+
38
+ The following 1 attestation matched the policy criteria
37
39
 
38
- PASSED: Verified SLSA provenance
40
+ - Attestation #1
41
+ - Build repo:..... launchdarkly/ruby-server-sdk-otel
42
+ - Build workflow:. .github/workflows/release-please.yml
43
+ - Signer repo:.... launchdarkly/ruby-server-sdk-otel
44
+ - Signer workflow: .github/workflows/release-please.yml
39
45
  ```
40
46
 
41
- Alternatively, to verify the provenance manually, the SLSA framework specifies [recommendations for verifying build artifacts](https://slsa.dev/spec/v1.0/verifying-artifacts) in their documentation.
47
+ For more information, see [GitHub's documentation on verifying artifact attestations](https://docs.github.com/en/actions/security-for-github-actions/using-artifact-attestations/using-artifact-attestations-to-establish-provenance-for-builds#verifying-artifact-attestations-with-the-github-cli).
42
48
 
43
- **Note:** These instructions do not apply when building our libraries from source.
49
+ **Note:** These instructions do not apply when building our libraries from source.
data/SECURITY.md CHANGED
@@ -1,5 +1,8 @@
1
1
  # Reporting and Fixing Security Issues
2
2
 
3
- Please report all security issues to the LaunchDarkly security team by submitting a bug bounty report to our [HackerOne program](https://hackerone.com/launchdarkly?type=team). LaunchDarkly will triage and address all valid security issues following the response targets defined in our program policy. Valid security issues may be eligible for a bounty.
3
+ **Do not open Issues or Pull Requests for security issues.**
4
+ This will make potential issues publicly visible before LaunchDarkly's Security Team can address them, which could lead to a compromise of the platform and negatively impact our customers.
4
5
 
5
- Please do not open issues or pull requests for security issues. This makes the problem immediately visible to everyone, including potentially malicious actors.
6
+ Security issues must be reported through our [Bug Bounty program](https://bugcrowd.com/engagements/launchdarkly-mbb-og), following the program policy, for triage and remediation by the LaunchDarkly Security Team. Valid security issues may be eligible for a bounty.
7
+
8
+ Please do not attempt to directly contact members of LaunchDarkly staff.
@@ -28,7 +28,7 @@ Gem::Specification.new do |spec|
28
28
  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
29
29
  spec.require_paths = ["lib"]
30
30
 
31
- spec.add_runtime_dependency "launchdarkly-server-sdk", "~> 8.4.0"
31
+ spec.add_runtime_dependency "launchdarkly-server-sdk", "~> 8.4"
32
32
  spec.add_runtime_dependency "opentelemetry-sdk", "~> 1.0", ">= 1.4.0"
33
33
 
34
34
  spec.add_development_dependency 'rake', '~> 13.0'
@@ -2,6 +2,6 @@
2
2
 
3
3
  module LaunchDarkly
4
4
  module Otel
5
- VERSION = '1.1.1' # x-release-please-version
5
+ VERSION = '1.1.2' # x-release-please-version
6
6
  end
7
7
  end
@@ -6,7 +6,10 @@
6
6
  "versioning": "default",
7
7
  "include-component-in-tag": false,
8
8
  "include-v-in-tag": false,
9
- "extra-files": ["PROVENANCE.md", "lib/ldclient-otel/version.rb"]
9
+ "extra-files": [
10
+ "PROVENANCE.md",
11
+ "lib/ldclient-otel/version.rb"
12
+ ]
10
13
  }
11
14
  }
12
15
  }
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: launchdarkly-server-sdk-otel
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.1
4
+ version: 1.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - LaunchDarkly
@@ -15,14 +15,14 @@ dependencies:
15
15
  requirements:
16
16
  - - "~>"
17
17
  - !ruby/object:Gem::Version
18
- version: 8.4.0
18
+ version: '8.4'
19
19
  type: :runtime
20
20
  prerelease: false
21
21
  version_requirements: !ruby/object:Gem::Requirement
22
22
  requirements:
23
23
  - - "~>"
24
24
  - !ruby/object:Gem::Version
25
- version: 8.4.0
25
+ version: '8.4'
26
26
  - !ruby/object:Gem::Dependency
27
27
  name: opentelemetry-sdk
28
28
  requirement: !ruby/object:Gem::Requirement