Skip to content

chore(release): v1.2.0 release date and live branch test environments (DX-31560) - #224

Merged
reeshika-h merged 2 commits into
developmentfrom
chore/DX-31560-release-date
Nov 12, 2026
Merged

reeshika-h merged 2 commits into
developmentfrom
chore/DX-31560-release-date

Conversation

@reeshika-h

@reeshika-h reeshika-h commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

What

Two changes for the v1.2.0 release of the branch-create environment list (DX-31560):

  1. Release date. The v1.2.0 changelog entry carried 28 Oct, the day the feature merged, and now sits above a Snyk release dated 2 Nov. Set it to 2026-11-12. No version change: 1.2.0 is already in Directory.Build.props and is not released yet.
  2. Live test fix. Contentstack005_BranchTest hard-coded the environment names development and staging. They do not exist on the stack the integration suite creates, so Test026_Should_Create_Branch_With_Two_Environment_Names failed with a 422 ("Environment 'development' was not found"). The class now creates two uniquely named environments in ClassInitialize and deletes them in ClassCleanup. The changelog test note is updated to match (it said the integration tests were "not run in this change").

Test code and changelog only. No change to the SDK.

Verified

  • With the fix, against api.contentstack.io (NA prod): the four environment-list tests (two names, [], unknown name, mixed names) pass, and the 191 tests in the login, organisation, stack and branch classes pass.
  • Without it, on pure development, Test026 fails as described above.
  • The test project builds with 0 errors. Unit tests: 1360 of 1360 pass.

Before releasing

If the release slips past 2026-11-12, re-date the v1.2.0 entry on the day you cut it.

🤖 Generated with Claude Code

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>
@reeshika-h
reeshika-h requested a review from a team as a code owner November 12, 2026 07:32
@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

…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>
@reeshika-h reeshika-h changed the title chore(release): set v1.2.0 release date to 2026-11-12 (DX-31560) chore(release): v1.2.0 release date and live branch test environments (DX-31560) Nov 12, 2026
@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 merged commit ae2c109 into development 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.

2 participants