Skip to content

Pre stage#1068

Open
vikrantraut-cstk wants to merge 377 commits into
mainfrom
pre-stage
Open

Pre stage#1068
vikrantraut-cstk wants to merge 377 commits into
mainfrom
pre-stage

Conversation

@vikrantraut-cstk
Copy link
Copy Markdown

No description provided.

shobhitupadhyayy and others added 30 commits March 6, 2026 13:47
…ema merging and UID handling; update ContentMapper to support nested modular blocks and prevent duplicate selections fix - CMG-812, CMG-818, CMG-823, CMG-824, CMG-831
…jsdom to 23.2.0, multer to 2.1.1, and rollup to 4.59.0; add overrides for various packages to ensure compatibility Snyk Issue Resolved
… and update docker-compose for security options
… and update docker-compose for security options
…ck mappings and improve nested field handling for nested group
…eak statements and enhancing button field handling for improved schema generation
Adds comprehensive unit test coverage including:
- Controller tests (auth, migration, org, projects, user, contentMapper)
- Service tests (auth, contentMapper, extension, globalField, marketplace, migration, org, projects, taxonomy, user)
- Middleware tests (auth, error, req-headers, unmatched-routes, uploadService)
- Model tests (FieldMapper, authentication, contentTypesMapper-lowdb, project-lowdb)
- Route tests (auth, contentMapper, migration, org, projects, user)
- Utility tests (async-router, auth, batch-processor, custom-errors, field-attacher, get-project, https, jwt, mimeTypes, pagination, sanitize-path, search, index)
- Validator tests (affix, affix-confirmation, auth, cms, destination-stack, file-format, fileformat-confirmation, index, project, stack)
- Test fixtures and setup configuration
- Vitest configuration
- GitHub Actions test workflow

Co-authored-by: Cursor <[email protected]>
…y checks, and source composition analysis

- Introduced a workflow to create Jira tickets automatically when GitHub issues are opened.
- Added a security policy scan to check for the presence of SECURITY.md and license files on pull request events.
- Implemented a source composition analysis scan using Snyk to identify vulnerabilities in the codebase.

These enhancements improve issue tracking and security compliance in the repository.
…y checks, and source composition analysis

- Introduced a workflow to create Jira tickets automatically when GitHub issues are opened.
- Added a security policy scan to check for the presence of SECURITY.md and license files on pull request events.
- Implemented a source composition analysis scan using Snyk to identify vulnerabilities in the codebase.

These enhancements improve issue tracking and security compliance in the repository.

Co-authored-by: Cursor <[email protected]>
- Updated GitHub Actions workflow to include separate jobs for API and UI tests, improving clarity and organization.
- Increased Node.js version in the workflow to 22 for better compatibility.
- Added Vitest configuration for UI testing, including coverage reporting.
- Introduced multiple unit tests for hooks, services, and components, ensuring comprehensive coverage and reliability.
- Updated package dependencies for testing libraries to the latest versions.

These changes enhance the testing framework and ensure robust coverage for both API and UI components.
…r improved dependency management during testing
…or improved compatibility with legacy peer dependencies during testing
- Updated auth and project validator tests to include the beforeAll hook for improved test setup.
- Added import of vi in the config fixture to facilitate mocking capabilities.

These changes improve the structure and functionality of the testing framework.
… Drupal documentation link

- Modified the test for VALIDATION_DOCUMENTATION_URL.drupal to check for 'Drupal.pdf' instead of an empty string, ensuring accurate validation of documentation links.
…ted ones

- Added @storybook/addons, @storybook/api, and related packages at version 6.5.16 for improved UI component development.
- Replaced the outdated redux version from @reduxjs/toolkit with a compatible version from @contentstack/venus-components.
- Updated dependencies for better compatibility and functionality across the UI components.
- Upgraded  to version 4.0.4 and  to version 5.0.4 in package-lock.json for improved compatibility.
- Updated  to version 10.2.4 and added new dependencies in package.json for enhanced functionality.
- Increased versions of  and  in upload-api to ensure compatibility with the latest features.
- Added overrides for several packages to maintain consistency across the project.

These changes enhance the overall stability and performance of the application.
feat: add Drupal support with MySQL configuration and update docker-c…
@vikrantraut-cstk vikrantraut-cstk requested a review from a team as a code owner May 13, 2026 08:54
@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 6 322 25 ✅ Passed
🟡 Medium Severity 3 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

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 2 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 322
  • Medium without fixes: 2
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

shobhit-cstk and others added 4 commits May 13, 2026 16:25
- Added mounting of app.json in docker-compose.yml for better configuration access.
- Updated setup-docker.sh to check for app.json existence and provide clearer prompts for MySQL host input.
- Introduced a utility function to resolve the app.json path dynamically, improving flexibility in locating the configuration file.
- Refactored auth.service.ts and user.service.ts to utilize the new app configuration path utility.
- Updated tests to reflect changes in user service behavior regarding app organization checks.
feat: enhance Docker setup and app configuration handling
@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 6 322 25 ✅ Passed
🟡 Medium Severity 3 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

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 2 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 322
  • Medium without fixes: 2
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

@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 6 322 25 ✅ Passed
🟡 Medium Severity 3 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

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 2 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 322
  • Medium without fixes: 2
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

yashin4112 and others added 9 commits May 14, 2026 15:50
fix: improve error handling in login response notification
…api and upload-api

- Upgraded @contentstack/cli to version 1.61.1 in both api and upload-api.
- Updated @wordpress/block-serialization-default-parser to version 5.46.0 in api.
- Updated @wordpress/block-library to version 9.46.0 and @wordpress/blocks to version 15.19.0 in upload-api.
- Bumped @babel/runtime to version 7.29.2 in upload-api.
- Added new dependency @arraypress/waveform-player version 1.2.1 in upload-api.
…kage-lock.json

- Added yaml package with version 2.4.2 to both package.json and package-lock.json.
- Updated existing yaml dependency version from 1.10.3 to 2.9.0 in package-lock.json, including new metadata for funding and binary.
fix: correct object assignment and improve nested group processing in…
@vikrantraut-cstk vikrantraut-cstk requested a review from a team as a code owner May 15, 2026 13:10
@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 4 327 25 ✅ Passed
🟡 Medium Severity 0 4 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

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 2 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 327
  • Medium without fixes: 4
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

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.