Skip to content

DX | 12-11-2026 | Release - #283

Merged
reeshika-h merged 19 commits into
masterfrom
development
Nov 12, 2026
Merged

reeshika-h merged 19 commits into
masterfrom
development

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

---- v1.16.0

OMpawar-21 and others added 19 commits August 24, 2026 13:47
chore: back-merge master into development
Brings back-merge branch up to date with development so master can be back-merged cleanly (DX-20927).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DX-20927 | Back-merge master into development
…-29683)

The SDK serializes request bodies with a default Gson converter, which drops
null values, so "field": null never reached the CMA and a field such as a
Number on a localized entry could not be cleared.

Add Contentstack.Builder.setSerializeNulls(boolean), off by default so
existing behavior is unchanged. When enabled, explicit nulls are sent for
every request made through the client.

Bump version to 1.15.0 and add a changelog entry.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
feat: add opt-in Builder.setSerializeNulls to send explicit nulls (DX-29683)
Branch create accepts an optional branch.publish_config.environments list of
environment names. The runtime already passes the body through unchanged, so
this change adds the Javadoc for the three behaviors (a list, [], and omitted),
unit tests that pin the request body and the mocked 422 and fetch paths, and
a live BranchAPITest that creates, fetches and deletes branches against a real
stack (it skips without credentials). The SDK adds no validation or length
limit; the API's error body is returned unchanged. Bumps the version to 1.16.0
and adds a changelog entry.

Refs: DX-31564

Co-authored-by: Raj Pandey <raj.pandey@contentstack.com>
Co-authored-by: Reeshika Hosmani <reeshika.hosmani@contentstack.com>
Co-authored-by: Aniket Shikhare <aniket.shikhare@contentstack.com>
Co-authored-by: Claude <noreply@anthropic.com>
Branch UIDs allow 15 lowercase letters and digits; the long run-id UIDs
would have made the create calls fail for the wrong reason. Also assert the
422 body names publish_config.environments and register created UIDs for
cleanup before asserting.

Refs: DX-31564

Co-authored-by: Raj Pandey <raj.pandey@contentstack.com>
Co-authored-by: Reeshika Hosmani <reeshika.hosmani@contentstack.com>
Co-authored-by: Aniket Shikhare <aniket.shikhare@contentstack.com>
Co-authored-by: Claude <noreply@anthropic.com>

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XifDUX2vy4ahCznNWQ2P3S
Refs: DX-31564

Co-authored-by: Raj Pandey <raj.pandey@contentstack.com>
Co-authored-by: Reeshika Hosmani <reeshika.hosmani@contentstack.com>
Co-authored-by: Aniket Shikhare <aniket.shikhare@contentstack.com>
Co-authored-by: Claude <noreply@anthropic.com>
…ranch-create-environments

feat(branch): environment list on branch create (DX-31564)
…in BranchAPITest

BranchAPITest used TestClient.getStack(), which sends the management token.
Branch create answered 401 (error 161) with it, and the test assumed the
'development' and 'production' environments exist on the stack.

The class now:
- logs in with EMAIL / PASSWORD and uses the apiKey header only;
- creates two environments whose names are unique to the run, and deletes
  them, with every created branch (force=true), and logs out in @afterall;
- polls fetch until a created branch is ready (bounded, 60s, 2s steps);
- treats a rejected create as no branch when fetch answers 422 with
  error_code 905, the same answer as a missing branch;
- adds TC-23 (create without publish_config) and TC-24 (environment name in
  a different case gets 422).

Without EMAIL, PASSWORD or apiKey in .env the class is skipped with a
"not run" message. TestClient gains public EMAIL and PASSWORD constants and
isApiKeyConfigured().

Refs: DX-31579

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ef6P4M5YRs6tDbdFqkvmZc
…api-test-login

fix(branch): log in with EMAIL/PASSWORD and manage own environments in BranchAPITest (DX-31579)
…-environments

feat(branch): optional environment list on branch create (DX-31560)
Resolved conflicts in changelog.md (kept v1.16.0; v1.15.0 takes master's
release date and Tests line) and pom.xml (kept version 1.16.0).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…opment-279

Back-merge master into development (1.15.0 Snyk fixes)
…ctor on (DX-31560)

BranchAPITest logs in with a plain email and password, so it cannot run on an
account with two-factor on: the API answers 401 error 294. Add an optional
MFA_SECRET to TestClient and pass it to client.login as mfaSecret when set, so
the SDK generates the one-time code. Without MFA_SECRET the plain login is
unchanged.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The v1.16.0 changelog entry carried the date the feature merged (28 Oct), which now
sits above a Snyk release dated 2 Nov. Set the date to the release date. No
version change: v1.16.0 is already the version in the repo and is not yet released.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…st-mfa-login

test(branch): log in with MFA_SECRET when the test account has two-factor on (DX-31560)
chore(release): set v1.16.0 release date to 2026-11-12 (DX-31560)
@snyk-io

snyk-io Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

@reeshika-h
reeshika-h marked this pull request as ready for review November 12, 2026 10:00
@reeshika-h
reeshika-h requested a review from a team as a code owner November 12, 2026 10:00
@reeshika-h
reeshika-h merged commit eeed666 into master Nov 12, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants