@dhis2/expression-parser 1.1.0-beta.9 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/README.md +15 -15
  2. package/expression-parser.js +1693 -1691
  3. package/expression-parser.js.map +1 -1
  4. package/expression-parser.mjs +1693 -1691
  5. package/expression-parser.mjs.map +1 -1
  6. package/kotlin-kotlin-stdlib.js +17 -17
  7. package/kotlin-kotlin-stdlib.js.map +1 -1
  8. package/kotlin-kotlin-stdlib.mjs +5 -5
  9. package/package.json +1 -1
package/README.md CHANGED
@@ -48,22 +48,22 @@ To select which expression is used the `Expression` is parameterized with a `Mod
48
48
  * `RULE_ENGINE_ACTION`: Computes a boolean, string, number or date from a rule
49
49
 
50
50
  ## Development
51
- This library implements the semantic release setup, which means that version numbers are not manually maintained but
52
- derived from the commit/PR history.
53
51
 
54
- Branches:
55
- - `main`: a push to `main` branch will trigger a new production release (both Maven and NPMJS).
56
- - `beta`: a push to `beta` branch will trigger a SNAPSHOT release in Maven and a new beta release in NPMJS.
52
+ ### Version
53
+ Library version is defined in the file `build.gradle.kts`. The version must be manually increased
54
+ and include the `-SNAPSHOT` suffix. Please make sure the version is updated before opening the PR.
57
55
 
58
- Version number are determined by the presence of commits with these suffixes:
59
- - `fix:`: it will increase the patch number.
60
- - `feat:`: it will increase the minor version number.
61
- - `feat!:`: it will increase the major version number.
56
+ ### Publications
62
57
 
63
- If there is not any commit with any of this tags between the previous version and the current commit, nothing will be published.
58
+ On merged pull request to `main`:
59
+ - Production release to Maven.
60
+ - Production release to NPMJS.
64
61
 
65
- Typical workflow:
66
- 1. Do work in a feature branch. There is no need to add tags to the commits.
67
- 2. Create a PR to `beta` branch including a tag in the PR title depending on the kind of changes.
68
- 3. Merge the PR using **Squash and merge**. It will publish a SNAPSHOT/BETA release if there is a version change.
69
- 4. Create a PR to `main` branch. Once merged, it will publish a production release.
62
+ On pull request creation/update:
63
+ - Snapshot release to Maven.
64
+
65
+ On demand:
66
+ - Beta releases to NPMJS can be triggered on demand by using the action "Publish NPM beta".
67
+ Please make sure you select the right branch in the selector.
68
+
69
+ Publication can be skipped by adding `[skip publish]` to the pull request title.