flowvault/v1.0.1

What's Changed

Added Support for FlowVauld

Full Changelog: flowvault/v1.0.0...flowvault/v1.0.1

flowvault/v1.0.0

What's Changed

• SK-2986 use admin service-account PAT for release version-bump push by @Devesh-Skyflow in #371
• Fix internal-release infinite loop on main ([skip ci] on version-bump commit) by @Devesh-Skyflow in #378
• SK-3002 release/26.8.1 by @skyflow-bharti in #386
• SK-3002 fix javadoc links blocking the flowvault public release by @Devesh-Skyflow in #400
• SK-3002 bump central-publishing-maven-plugin to 0.11.0 for the Portal API by @Devesh-Skyflow in #402

Full Changelog: 2.1.1...flowvault/v1.0.0

3.0.0-beta.13

Configurable connect / read / write timeouts (v3)

Building on the overall timeout and retry controls from 3.0.0-beta.12, you can now tune the
per-attempt HTTP phase timeouts — connection, read, and write — at the client level (all vaults)
or per vault (overrides the client-wide value, per field).

Skyflowclient = Skyflow.builder()
.addSkyflowCredentials(credentials)
.timeout(60) // overall call ceiling (seconds) — bounds the whole call incl. retries
.connectTimeout(10) // per-attempt connect (seconds)
.readTimeout(15) // per-attempt read (seconds)
.writeTimeout(10) // per-attempt write (seconds)
.maxRetries(2) // retry attempts (default 0 = off)
.addVaultConfig(vaultConfig) // e.g. vaultConfig.setConnectTimeout(5) to override one vault
.build();

Setting	Unit	Default
timeout	seconds	60
connectTimeout	seconds	10
readTimeout	seconds	10
writeTimeout	seconds	10

How the four relate:timeout is the total ceiling for the whole call (all attempts + backoff).
connectTimeout / readTimeout / writeTimeout each bound a single phase of one attempt — because
they are per attempt, their sum across retries can exceed timeout, but timeout always wins and
cuts the call off.

• Precedence: per-vault → client-wide → default, resolved per field.
• Available at two levels: client-wide via Skyflow.builder() (.connectTimeout(int),
  .readTimeout(int), .writeTimeout(int)) and per vault via VaultConfig
  (.setConnectTimeout(int), .setReadTimeout(int), .setWriteTimeout(int)).

Documentation

• README now documents the full timeout & retry configuration, including a "how the four timeouts
  relate" guide, and TimeoutAndRetryConfigExample shows the new settings.

Full Changelog: 3.0.0-beta.12...3.0.0-beta.13

3.0.0-beta.12

What's Changed

Configurable HTTP timeouts & retries

Tune the SDK's timeout and retry behavior at the client level (all vaults) or per vault (overrides the client-wide value, per field).

Skyflowclient = Skyflow.builder()
.addSkyflowCredentials(credentials)
.timeout(30) // overall call timeout (seconds)
.maxRetries(2) // retry attempts (default 0 = off)
.initialRetryDelayMillis(500) // base backoff (ms)
.maxRetryDelayMillis(2000) // backoff cap (ms)
.addVaultConfig(vaultConfig) // e.g. vaultConfig.setTimeout(10) to override one vault
.build();

Setting	Unit	Default
timeout	seconds	60
maxRetries	count	0 (retries off)
initialRetryDelayMillis	ms	500
maxRetryDelayMillis	ms	2000

• Precedence: per-vault → client-wide → default.
• Retries (when enabled) apply to 408 / 429 / 5xx

Upsert defaults

• upsertType is now optional and defaults to UPDATE. Set REPLACE explicitly when you need it.

2.1.1

What's Changed

Dependency maintenance

• Upgradedjackson-datatype-jdk8 and jackson-datatype-jsr3102.17.2 → 2.18.6 (aligns with jackson-databind).
• Upgradeddotenv-java2.2.0 → 3.2.0.
• Dropped commons-codec — Base64 handling now uses the JDK-native java.util.Base64.

Documentation & samples

• Fixed gaps in the README and code samples.
• New sample: Detect ReidentifyText example; refreshed the Detokenize and Get examples.

Full Changelog: 2.1.0...2.1.1

1.15.1

What's Changed

• SK-1786 common workflow for internal and public release by @skyflow-shravan in #137
• SK-1407 Add PR Template by @skyflow-vivek in #106
• SK-1633 Run Endor labs scan to identify security vulnerabilities by @skyflow-vivek in #147
• SK-1633 Fix failure in endorlabs workflow by @skyflow-vivek in #148
• SK-1633 Add GPG secrets to endorlabs workflow by @skyflow-vivek in #149
• SK-1633 Fix failures in workflow by @skyflow-vivek in #150
• SK-1633 Add permissions for endorlabs scan by @skyflow-vivek in #151
• SC-5146:Update semgrep.yml by @Revanthathreya in #162
• SC-5790:Create Gitleaks.yml by @Revanthathreya in #175
• Public Release/26.5.6 by @Devesh-Skyflow in #329
• Public Release/26.5.6 (#329) by @Devesh-Skyflow in #331
• Devesh/fix v1 release by @Devesh-Skyflow in #332
• Devesh/fix v1 release by @Devesh-Skyflow in #333
• Devesh/fix v1 release by @Devesh-Skyflow in #334

Full Changelog: 1.15.0...1.15.1

2.1.0

What's Changed

• Credential field aliases — BearerToken, SignedDataTokens, and Credentials now accept
  camelCase credential keys (clientId, keyId, tokenUri) alongside the legacy all-caps forms
  (clientID, keyID, tokenURI). Both forms work; legacy forms emit a deprecation warning.
• getByot() — new canonical method on TokenMode; getBYOT() retained as a deprecated delegate.
• setLogLevel() — new canonical method on Skyflow; updateLogLevel() retained as a deprecated delegate.
• downloadUrl — new canonical field on GetRequest and DetokenizeRequest; downloadURL retained as deprecated.
• skyflowId normalisation — Get and Query responses now return skyflowId (camelCase)
  in addition to skyflow_id for backward compatibility.

Deprecations

Deprecated	Replacement
clientID / keyID / tokenURI in credentials	clientId / keyId / tokenUri
getBYOT()	getByot()
updateLogLevel()	setLogLevel()
downloadURL in GetRequest / DetokenizeRequest	downloadUrl
skyflow_id in response maps	skyflowId

All deprecated forms continue to work and emit a WARN-level log message.
They will be removed in a future major release.

Full Changelog: 2.0.4...2.1.0

3.0.0-beta.11

What's Changed

Added

• Custom request headers support: You can now pass custom HTTP headers with individual API requests. This enables use cases like tracing, correlation IDs, and downstream system integration without modifying global client configuration. (#304)

Full Changelog: 3.0.0-beta.10...3.0.0-beta.11

2.0.4

What's Changed

Added

• Context object support: The context field in bearer token requests now accepts a dictionary (key-value object) in addition to a plain string. This allows you to pass structured metadata — such as user attributes or access conditions — directly to Conditional Data Access policies. (#301)

Fixed

• Improved client stability: Resolved an issue with internal client re-initialization that could cause stale connections under certain authentication refresh scenarios. (#301)

Full Changelog: 2.0.3...2.0.4

3.0.0-beta.10

What's Changed

Changed

• Client initialization: Reduced startup overhead by deferring non-essential setup until the first API call. (#298)

Full Changelog: 3.0.0-beta.9...3.0.0-beta.10