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
  • Steps
  • Outcome
  1. Coder devtools - CDT
  2. User guide

Release a webpackage

PreviousBulk upload of webpackagesNextUpdate the RTE version of a webpackage

Last updated 6 years ago

When releasing a webpackage to need to:

  1. Check if all dependencies are not under development

  2. Update the current version to a fixed version; i.e., without the -SNAPSHOT suffix

  3. Upload the webpackage to a store

  4. Update the current version to a valid next development version, since no changes can be uploaded to fixed versions

The offers you the +webpackage-release task to release a webpackage. Actually, this task uses three other tasks to perform each step:

  1. The task to perform steps 1. and 2.

  2. The task to perform step 3.

  3. The to perform step 4.

Steps

You should run the task within the CDT folder (normally it is called devtools) as follows:

grunt  +webpackage-release

Then, each task will be run in the order presented above.

Click on the links provided above for each subtask to see further details about each step.

Outcome

Your webpackage will be uploaded to a store with a fixed version and the manifest.webpackage file will end up with the correct next development version.

CDT
_webpackage-prepareRelease
+webpackage-upload
_webpackage-updateToNextVersion