Skip to content

Releases: contentstack/migration-v2

v1.0.1

13 Jun 17:54
@umeshmore45 umeshmore45
v1.0.1
eb97a5e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.0.1 Latest
Latest

Key Changes

.talismanrc

  • Added new file checksums for:
    • upload-api/src/helper/index.ts
    • upload-api/package-lock.json
    • api/package-lock.json
  • Tightens secret scanning and integrity verification for updated files.

README.md

  • Removed CLI Setup Instructions:
    The section describing pnpm installation and npm run setup-repo was deleted.
    Documentation now focuses on available scripts and configuration.

api/package.json & api/package-lock.json

  • Dependency Updates:
    • Upgraded @contentstack/cli-utilities from ^1.11.1 to ^1.12.0
    • Indirect upgrades for sub-dependencies, including:
      • @contentstack/management to ~1.21.4/1.21.6
      • @contentstack/marketplace-sdk to ^1.2.8
      • @oclif/core to ^4.3.0
      • axios to ^1.9.0
      • dotenv to ^16.5.0
      • papaparse to ^5.5.3
      • Added husky (^9.1.7)
      • Multiple brace-expansion upgrades
  • Improves security, stability, and compatibility.

upload-api/package-lock.json

  • Dependency Upgrades:
    • Multiple upgrades for brace-expansion and related packages to address security advisories.

upload-api/src/helper/index.ts

  • Refactored Zip Extraction Logic:
    • Always prepends the main folder name to extracted files unless already present.
    • Skips writing files/directories that match the Mac OS X resource folder.
    • Cleans up logic for handling zip files, ensuring robust extraction for various structures.

Impact

  • Security: Improved dependency management and secret scanning.
  • Reliability: More robust zip extraction logic, especially for edge cases and Mac OS X files.
  • Maintainability: Codebase is cleaner, with clearer documentation and logic.
Assets 2
Loading

v1.0.0

10 Jun 09:19
@umeshmore45 umeshmore45
v1.0.0
677a931
Compare
Choose a tag to compare
v1.0.0

Release v1.0.0

We are excited to announce the release of v1.0.0 for the contentstack/migration-v2 repository!

Summary of Notable Changes

Added

  • SECURITY.md: Added a security policy and contact instructions.
  • CODEOWNERS: Added security-admin as code owner for all files.
  • api/package-lock.json: Locked dependencies for the API package.

Changed

  • .talismanrc:
    • Now includes version information and additional file checksums, especially for various package-lock.json files across the project.
    • Expanded ignore configuration for security scan-related files.

Details by File

  • Security & Licensing

    • Added SECURITY.md with responsible disclosure policy and contact.
    • Project now has a top-level CODEOWNERS file specifying security-admin as the owner.

  • Source Control & Configuration

    • Expanded .gitignore to ignore .vscode, but now tracks more previously ignored files (e.g., *.zip and package-lock.json).
    • .talismanrc improvements to cover more files for secret scanning.
    • Removed .vscode workspace recommendations and settings to reduce editor-specific configuration in the repo.

  • Dependency Management

    • Added api/package-lock.json (and several other package-lock files, referenced in .talismanrc) for reproducible builds.

Impact

  • Security and compliance improvements: Clearer code ownership, license, and security policy.
  • Dependency and configuration management: Improved reproducibility and auditing.
  • Editor experience: Removed VSCode-specific settings/recommendations for a more editor-agnostic repo.

View the full diff for more details

What's Changed

Full Changelog: v1.0.0-beta...v1.0.0

Contributors

umeshmore45 and sauravraw
Loading

v1.0.0-beta: Core Modules & CMS Connectors

13 May 14:32
@umeshmore45 umeshmore45
v1.0.0-beta
053e6aa
Compare
Choose a tag to compare
v1.0.0-beta: Core Modules & CMS Connectors

📌 Version: v1.0.0-beta (Beta Release)

This release includes the foundational components of the migration platform with support for multiple CMSs and initial migration flows.

✅ Included Modules and Features

⚠️ Known Limitations (Beta)

  • Contentful Connector
  1. Not handle the use case of deletion of existing destination stack in runtime
  2. Content mapper module | existing stack | existing content type mapped | Modular blocks, taxonomy these fields can be matched with Single Line Textbox field
  3. Content Type Migration Limitations in Test Stacks
  4. When migrating content types in a test stack, the handling of attached references depends on your organization's reference limit:
  5. Organizations with a reference limit of 50: Full data migration is supported if a content type has more than 10 references.
  6. Organizations with a reference limit of 10: If a content type has more than 10 references, only the 'title' and 'URL' fields will be migrated.
  7. Issue: Data migration may encounter unforeseen problems if the Contentful data contains duplicate UIDs.
  • Sitecore Connector

  1. Runtime Deletion Not Handled
    The system does not handle the deletion of an existing destination stack during runtime.

  2. Content Type Migration Limitations in Test Stacks
    When migrating content types in a test stack, the behavior depends on your organization's reference limits:

    • Organizations with a reference limit of 50:
      Full data migration is supported even if a content type has more than 10 references.

    • Organizations with a reference limit of 10:
      If a content type has more than 10 references, only the 'title' and 'URL' fields will be migrated.

  • Wordpress Connector

  1. Not supporting WordPress dynamic content models

  2. Supports only the basic data migration process

  3. Does not handle the use case of deletion of existing destination stack at runtime

  4. Content Type Migration Limitations in Test Stacks
    4.1 When migrating content types in a test stack, the handling of attached references depends on your organization's reference limit:

    4.2 Organizations with a reference limit of 50:
    Full data migration is supported if a content type has more than 10 references.

    4.3 Organizations with a reference limit of 10:
    If a content type has more than 10 references, only the 'title' and 'URL' fields will be migrated.

What's Changed

Read more

Contributors

snehalsankhe, sayalijoshi27, and 13 other contributors
Loading