Documentation
Primary version
Primary version
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  1. Coder devtools - CDT
  2. Contributor guide

Checklist for releasing a new webpackage.modelVersion

PreviousContributor guideNextTerms and concepts

Last updated 6 years ago

Releasing a new version of the webpackage.modelVersion can have an impact on several artifacts of the Cubbles Platform. Below is a checklist for adjusting these artifacts before releasing a new webpackage.modelVersion.

  1. cubx-webpackage-document-api

    Create a new release on GitHub for the repository at . This repository contains the source code of the cubx-webpackage-document-api npm package. It holds the manifest.webpackage schema file and the functionality to validate manifest.webpackage files against the schema.

  2. cubbles-coder-devtools

    Check if the grunt tasks of the npm package require changes. If so, apply these changes and release a new version of the cubbles-coder-devtools package.

  3. cubx-webpackage-version-converter

    Adjust the npm package which holds functionality to convert existing webpackages using an old webpackage.modelVersion to the current webpackage.modelVersion. Apply changes if necessary and release a new version.

  4. cubx-grunt-webpackage-version-converter

    Check if the npm package still works with the adjusted version of the cubx-webpackage-version-converter. If necessary, apply changes and release the new version.

  5. cubx-grunt-webpackage-scaffold

    1. Update schema references in lib/config/* files.

    2. Adjust (file) structure if necessary

    3. Adjust HTML templates if there are changes in Cubbles TAG API

    4. Use the latest cubx-webpackage-viewer

    5. Use the latest cubx.core.rte

    6. Release a new version of the npm package

  6. cubx-wct-scaffolder

    If necessary adjust the used npm package and release a new version.

  7. cubx-grunt-wct-scaffolder

    Check if the changes on cubx-wct-scaffolder broke functionality of the npm package. If so, adjust it and release a new version.

  8. generator-cubbles

    Use the latest version of the cubbles-coder-devtools in the npm package. Release a new version on npmjs.org.

  9. cubx.core.rte

    Several modules might need adjustments to enable the support of a new webpackage.modelVersion in :

    • Cubbles TAG API

    • CRC (allowed modelVersion)

    • DependencyManager

    • ManifestConverter

    • Cache

    • ManifestProcessor

    • CRC-Loader

    • CIF

  10. cubbles-test

    • Update all webpackages to the new rte version

    • Test them

    • Publish a fixed release of all webpackages

    • Change the version of all webpackages to the next SNAPSHOT version

https://github.com/cubbles/cubx-webpackage-document-api
cubbles-coder-devtools
cubx-webpackage-version-converter
cubx-grunt-webpackage-version-converter
cubx-grunt-webpackage-scaffold
cubx-wct-scaffolder
cubx-grunt-wct-scaffolder
generator-cubbles
RTE