Documentation
rte_2x
developPrimary versionrte_2xvuepress-migration
rte_2x
developPrimary versionrte_2xvuepress-migration
  • 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
  • Purpose
  • Steps
  • Outcome
  • The npm module version
  1. Coder devtools - CDT
  2. User guide

Update webpackage to the next development version

PreviousPrepare a webpackage to be releasedNextGenerate a test environment for a component

Last updated 5 years ago

The offers you the _webpackage-prepareRelease task to update the version of your current webpackage to the next development version as follows:

  • Using a version provided by you, or

  • Generating a SNAPSHOT version increasing the second digit of the current version (corresponds to the minor version in ).

Purpose

To show how to use the _webpackage-updateToNextVersion task to prepare a webpackage to be released.

Steps

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

grunt  _webpackage-updateToNextVersion

Then, you should provide the next development version to be used. Remember that it should be a digit, three or two dot-separated digits with a -SNAPSHOT suffix (e.g. 1-SNAPSHOT, 3.1-SNAPSHOT, 2.0.3-SNAPSHOT). Or you can use the generated value (displayed in parenthesis) by pressing Enter. For instance, in the code below the suggested version is 0.2.0-SNAPSHOT:

? Please type the next development version to be set to the webpackage: (0.2.0-SNAPSHOT)

If the provided version (if any) is correct, the process will finish. Otherwise, you will be prompted with a message indicating the error and how to solve it. After solving the error, you should run the task again.

Outcome

The version of your webpackage will be updated in the manifest.webpackage file.

The npm module version

You can use an npm module that serves the same purposes called . The module can be used from the command line or in a node script.

CDT
semantic versioning
cubx-prepare-webpackage-release