Skip to content

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

Merged
reeshika-h merged 13 commits into
mainfrom
development
Nov 12, 2026
Merged

reeshika-h merged 13 commits into
mainfrom
development

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

---- v1.2.0

reeshika-h and others added 13 commits August 3, 2026 13:45
chore: back-merge main into development
Brings back-merge branch up to date with development so main can be back-merged cleanly (DX-20927).

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

The integration project has not compiled since the MSTest 3.x → 4.x bump.
CI never caught it: unit-test.yml runs Scripts/run-unit-test-case.sh, which
builds and tests only Contentstack.Management.Core.Unit.Tests, so the
integration project is never compiled and rotted silently.

Three removed APIs, 49 call sites:

* ClassCleanupBehavior no longer exists — [ClassCleanup] always runs at end
  of class in MSTest 4, so the argument is dropped with no change in
  behaviour.
* Assert.ThrowsException<T> / ThrowsExceptionAsync<T> are gone. Replaced
  with ThrowsExactly<T> / ThrowsExactlyAsync<T>, NOT Throws<T>: the old API
  asserted the exception type was exactly T, while Throws<T> also accepts
  subclasses. A bulk rename to Throws would have compiled cleanly and
  silently weakened all 47 assertions.
* Assert.Fail(string, params object[]) is gone. It used to format the
  message with the parameters, so the call site formats explicitly to keep
  the same output.

Verified: the project builds with 0 errors, and the unit suite is unaffected
(1350/1350 passing, unchanged by this commit).

Follow-up worth doing separately: add a compile-only step for the
integration project to CI, or this recurs on the next MSTest bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…t-compat

fix(tests): restore MSTest 4 compatibility in the integration test project
Branch create can now clone only the environments a caller needs. BranchModel gains
PublishConfig (BranchPublishConfigModel) with an Environments list of environment names,
not UIDs. Two names clone only those two; an empty list clones none; leaving PublishConfig
unset sends the same body as before and clones all environments.

The SDK passes the list through unvalidated, adds no length limit, and surfaces the API's
422 error unchanged (ContentstackErrorException with message, error code and errors); no
branch is created on rejection. A fetched branch carries the list the API returns.

Adds the create XML docs for these behaviors, unit tests for the request body (two names,
empty list, unset), the 422 path and fetch deserialization, and integration tests for two
names, an empty list, an unknown name and a mix (written, not run). Bumps the version to
1.2.0 and adds a changelog entry.

Refs: DX-31565

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-create-environments

feat(branch): add optional environment list to branch create (DX-31565)
…-environments

feat(branch): optional environment list on branch create (DX-31560)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ment-222

Back-merge main into development
The v1.2.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.2.0 is already the version in the repo and is not yet released.

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

Contentstack005_BranchTest hard-coded the environment names development and
staging, which do not exist on the stack the integration suite creates, so
Test026 (create with two environment names) failed with a 422 "Environment
'development' was not found". Create two uniquely named environments in
ClassInitialize and delete them in ClassCleanup, and describe it in the v1.2.0
changelog test notes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore(release): v1.2.0 release date and live branch test environments (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 32a5326 into main Nov 12, 2026
10 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.

4 participants