Merge pull request #633 from vizzuhq/update3

Update dependencies

Author: veghdev

.clang-format

@@ -49,7 +49,7 @@ IndentExternBlock: NoIndent
 KeepEmptyLinesAtTheStartOfBlocks: true
 SpacesInContainerLiterals: false
 SpaceAfterTemplateKeyword: true
-AllowShortLambdasOnASingleLine: None
+AllowShortLambdasOnASingleLine: Empty
 AlignAfterOpenBracket: DontAlign
 
 IncludeCategories:

.eslintrc.cjs

@@ -6,7 +6,7 @@ on:
 
 jobs:
     publish:
-        runs-on: ubuntu-22.04
+        runs-on: ubuntu-24.04
 
         steps:
             - name: Trigger Cloud Build

.github/workflows/cd.yml

@@ -1,20 +1,15 @@
 name: Docker publish vizzu-dev-desktop
 
 on:
-    pull_request:
-        branches-ignore:
-            - main
-        paths:
-            - '**/vizzu-dev-desktop'
-            - '**/docker-vizzu-dev-desktop.yml'
+    workflow_dispatch:
 
 jobs:
     publish:
-        runs-on: ubuntu-22.04
+        runs-on: ubuntu-24.04
 
         steps:
             - name: Checkout repo
-              uses: actions/checkout@v3
+              uses: actions/checkout@v4
               with:
                   fetch-depth: 1
 
@@ -24,6 +19,6 @@ jobs:
             - name: Build and Publish
               run: |
                   IMAGE="vizzu-dev-desktop"
-                  IMAGE_NAME="vizzu/$IMAGE:0.16"
+                  IMAGE_NAME="vizzu/$IMAGE:0.17"
                   docker build -t $IMAGE_NAME -f tools/ci/docker/$IMAGE .
                   docker push $IMAGE_NAME

.github/workflows/docker-vizzu-dev-desktop.yml

@@ -1,20 +1,15 @@
 name: Docker publish vizzu-dev-wasm
 
 on:
-    pull_request:
-        branches-ignore:
-            - main
-        paths:
-            - '**/vizzu-dev-wasm'
-            - '**/docker-vizzu-dev-wasm.yml'
+    workflow_dispatch:
 
 jobs:
     publish:
-        runs-on: ubuntu-22.04
+        runs-on: ubuntu-24.04
 
         steps:
             - name: Checkout repo
-              uses: actions/checkout@v3
+              uses: actions/checkout@v4
               with:
                   fetch-depth: 1
 
@@ -24,6 +19,6 @@ jobs:
             - name: Build and Publish
               run: |
                   IMAGE="vizzu-dev-wasm"
-                  IMAGE_NAME="vizzu/$IMAGE:0.16"
+                  IMAGE_NAME="vizzu/$IMAGE:0.17"
                   docker build -t $IMAGE_NAME -f tools/ci/docker/$IMAGE .
                   docker push $IMAGE_NAME

.github/workflows/docker-vizzu-dev-wasm.yml

@@ -7,7 +7,7 @@ on:
 jobs:
     notify_merged_pr:
         name: Notify on merged PR
-        runs-on: ubuntu-22.04
+        runs-on: ubuntu-24.04
         if: ${{ github.event.pull_request.merged == true }}
         steps:
             - uses: abinoda/slack-action@master

.github/workflows/slack.yml

@@ -30,7 +30,7 @@ community include:
 - Being respectful of differing opinions, viewpoints, and experiences
 - Giving and gracefully accepting constructive feedback
 - Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
+    and learning from the experience
 - Attempting collaboration before conflict
 - Sharing your knowledge and ask questions
 - Giving credit when the credit is deserved
@@ -40,17 +40,17 @@ Examples of unacceptable behavior include:
 
 - Violence, threats of violence, or inciting others to commit self-harm
 - The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
+    advances
 - Trolling, intentionally spreading misinformation, insulting/derogatory
-  comments, and personal or political attacks
+    comments, and personal or political attacks
 - Public or private harassment
 - Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
+    address, without explicit permission
 - Represent someone else’s work or words as your own
 - Abuse of the reporting process to intentionally harass or exclude others
 - Advocating for, or encouraging, any of the above behavior
 - Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+    professional setting
 
 ## Enforcement Responsibilities
 
@@ -87,29 +87,29 @@ Project maintainers will follow these Community Impact Guidelines in determining
 the consequences for any action they deem in violation of this Code of Conduct:
 
 - Correction Community Impact: Use of inappropriate language or other behavior
-  deemed unprofessional or unwelcome in the community. Consequence: A private,
-  written warning from Project maintainers, providing clarity around the nature
-  of the violation and an explanation of why the behavior was inappropriate. A
-  public apology may be requested.
+    deemed unprofessional or unwelcome in the community. Consequence: A private,
+    written warning from Project maintainers, providing clarity around the
+    nature of the violation and an explanation of why the behavior was
+    inappropriate. A public apology may be requested.
 - Warning Community Impact: A violation through a single incident or series of
-  actions. Consequence: A warning with consequences for continued behavior. No
-  interaction with the people involved, including unsolicited interaction with
-  those enforcing the Code of Conduct, for a specified period of time. This
-  includes avoiding interactions in community spaces as well as external
-  channels like social media. Violating these terms may lead to a temporary or
-  permanent ban.
+    actions. Consequence: A warning with consequences for continued behavior. No
+    interaction with the people involved, including unsolicited interaction with
+    those enforcing the Code of Conduct, for a specified period of time. This
+    includes avoiding interactions in community spaces as well as external
+    channels like social media. Violating these terms may lead to a temporary or
+    permanent ban.
 - Temporary Ban Community Impact: A serious violation of community standards,
-  including sustained inappropriate behavior. Consequence: A temporary ban from
-  any sort of interaction or public communication with the community for a
-  specified period of time. No public or private interaction with the people
-  involved, including unsolicited interaction with those enforcing the Code of
-  Conduct, is allowed during this period. Violating these terms may lead to a
-  permanent ban.
+    including sustained inappropriate behavior. Consequence: A temporary ban
+    from any sort of interaction or public communication with the community for
+    a specified period of time. No public or private interaction with the people
+    involved, including unsolicited interaction with those enforcing the Code of
+    Conduct, is allowed during this period. Violating these terms may lead to a
+    permanent ban.
 - Permanent Ban Community Impact: Demonstrating a pattern of violation of
-  community standards, including sustained inappropriate behavior, harassment of
-  an individual, or aggression toward or disparagement of classes of
-  individuals. Consequence: A permanent ban from any sort of public interaction
-  within the community.
+    community standards, including sustained inappropriate behavior, harassment
+    of an individual, or aggression toward or disparagement of classes of
+    individuals. Consequence: A permanent ban from any sort of public
+    interaction within the community.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good
 faith may face temporary or permanent repercussions as determined by other

CODE_OF_CONDUCT.md

@@ -23,11 +23,11 @@ mind, that's awesome and we are very interested in hearing about it.
 ### Development environment
 
 The following steps demonstrate how to set up the development environment on an
-`Ubuntu` `22.04` operating system. However, the process can be adapted for other
+`Ubuntu` `24.04` operating system. However, the process can be adapted for other
 operating systems as well.
 
 To contribute to the `JavaScript` part of the project, it is recommended to use
-`Node.js` `18`.
+`Node.js` `22`.
 
 Run the following command to install the `JavaScript` development dependencies:
 
@@ -41,7 +41,7 @@ the command `npm run lock:js`.
 
 However, for the documentation we are also using `Python`. If you plan to
 contribute to this part of the project, you will need `Python`, preferably
-version `3.10`.
+version `3.13`.
 
 Run the following command to install the `Python` development dependencies:
 
@@ -59,6 +59,14 @@ To contribute to the `C++` part of the project, it is recommended to use
 `Docker`, but based on the `Dockerfiles` below, you can also configure the
 necessary dependencies on your local machine.
 
+**Note:** If you need to change the environment you need to manually update the
+docker images:
+
+```sh
+gh workflow run "Docker publish vizzu-dev-desktop" --ref <branch>
+gh workflow run "Docker publish vizzu-dev-wasm" --ref <branch>
+```
+
 Run the following commands to build and run the `Desktop` version's development
 environment
 
@@ -70,7 +78,7 @@ docker run -i -t -v .:/workspace vizzu/vizzu-dev-desktop bash
 or you can use a specific version of the prebuilt image:
 
 ```sh
-docker run -i -t -v .:/workspace vizzu/vizzu-dev-desktop:0.16 bash
+docker run -i -t -v .:/workspace vizzu/vizzu-dev-desktop:0.17 bash
 ```
 
 Run the following commands to build and run the `WASM` version's development
@@ -84,7 +92,7 @@ docker run -i -t -v .:/workspace vizzu/vizzu-dev-wasm bash
 or you can use a specific version of the prebuilt image:
 
 ```sh
-docker run -i -t -v .:/workspace vizzu/vizzu-dev-wasm:0.16 bash
+docker run -i -t -v .:/workspace vizzu/vizzu-dev-wasm:0.17 bash
 ```
 
 ### Building the project
@@ -131,9 +139,10 @@ Run the following script in the running `vizzu-dev-wasm` container to build the
 **Note:** To debug WASM version under Chrome:
 
 - set Chrome/DevTools/Settings/Experiments/'WebAssembly Debugging: Enable DWARF
-  support' to true
-- set \[repo\]/project/cmake/emcc.txt: CMAKE_EXE_LINKER_FLAGS_DEBUG
-  --source-map-base to the URL where the browser can find cvizzu.wasm.map file.
+    support' to true
+- set [repo]/project/cmake/emcc.txt: CMAKE_EXE_LINKER_FLAGS_DEBUG
+    --source-map-base to the URL where the browser can find cvizzu.wasm.map
+    file.
 
 #### Building npm package
 
@@ -250,17 +259,17 @@ sometimes unstable changes.
 
 - build from the `HEAD` commit of the main branch:
 
-  https://vizzu-lib-main.storage.googleapis.com/lib/vizzu.js
+    https://vizzu-lib-main.storage.googleapis.com/lib/vizzu.js
 
-  and the minified, boundled version:
+    and the minified, boundled version:
 
-  https://vizzu-lib-main.storage.googleapis.com/lib/vizzu.min.js
+    https://vizzu-lib-main.storage.googleapis.com/lib/vizzu.min.js
 
 - all builds of the past 30 days:
 
-  https://vizzu-lib-main-sha.storage.googleapis.com/lib-HASH/vizzu.js
+    https://vizzu-lib-main-sha.storage.googleapis.com/lib-HASH/vizzu.js
 
-  where `HASH` is the first 7 character of the commit's git hash.
+    where `HASH` is the first 7 character of the commit's git hash.
 
 ### Documentation
 
@@ -297,12 +306,12 @@ To release `Vizzu`, follow the steps below:
 - You should increase the version number in `src/chart/main/version.cpp`.
 
 - If the major or minor version has changed, increase the version in
-  `.github/workflows/docker-vizzu-dev-desktop.yml`,
-  `.github/workflows/docker-vizzu-dev-wasm.yml`,
-  `tools/ci/gcp/cloudbuild/cloudbuild.yaml` and `CONTRIBUTING.md`.
+    `.github/workflows/docker-vizzu-dev-desktop.yml`,
+    `.github/workflows/docker-vizzu-dev-wasm.yml`,
+    `tools/ci/gcp/cloudbuild/cloudbuild.yaml` and `CONTRIBUTING.md`.
 
 - Set the release and release date in `CHANGELOG.md`, under the `Unreleased`
-  title.
+    title.
 
 - Create the release notes from `CHANGELOG.md` and publish the new release on
-  [Releases](https://github.com/vizzuhq/vizzu-lib/releases).
+    [Releases](https://github.com/vizzuhq/vizzu-lib/releases).

CONTRIBUTING.md

@@ -1,4 +1,4 @@
 Vizzu
-Copyright 2021-2024 Vizzu Inc.
+Copyright 2021-2025 Vizzu Inc.
 
 This product includes software developed at Vizzu Inc.

NOTICE

@@ -9,26 +9,26 @@ send a pull request.
 Official:
 
 - Bindings
-  - \[[ipyvizzu](https://github.com/vizzuhq/ipyvizzu)\] **Jupyter Notebook**
-    integration for Vizzu
+    - \[[ipyvizzu](https://github.com/vizzuhq/ipyvizzu)\] **Jupyter Notebook**
+        integration for Vizzu
 - Extensions
-  - \[[vizzu-story-js](https://github.com/vizzuhq/vizzu-story-js)\]
-    **Presentation** control extension for Vizzu data stories
-  - \[[vizzu-ext-js-scrollytelling](https://github.com/vizzuhq/vizzu-ext-js-scrollytelling)\]
-    **ScrollyTelling** extension for articles with Vizzu
+    - \[[vizzu-story-js](https://github.com/vizzuhq/vizzu-story-js)\]
+        **Presentation** control extension for Vizzu data stories
+    - \[[vizzu-ext-js-scrollytelling](https://github.com/vizzuhq/vizzu-ext-js-scrollytelling)\]
+        **ScrollyTelling** extension for articles with Vizzu
 - Templates
-  - \[[vizzu-webpack-demo](https://github.com/vizzuhq/vizzu-webpack-demo)\]
-    Howto and example for using Vizzu with **Webpack**
-  - \[[vizzu-react-example](https://github.com/vizzuhq/vizzu-react-example)\]
-    Howto and example for using Vizzu with **React**
-  - \[[vizzu-vite-demo](https://github.com/vizzuhq/vizzu-vite-demo)\] Howto and
-    example for using Vizzu with **Vite**
-  - \[[vizzu-pyscript-example](https://github.com/vizzuhq/vizzu-pyscript-example)\]
-    Howto and example for using Vizzu in **PyScript**
+    - \[[vizzu-webpack-demo](https://github.com/vizzuhq/vizzu-webpack-demo)\]
+        Howto and example for using Vizzu with **Webpack**
+    - \[[vizzu-react-example](https://github.com/vizzuhq/vizzu-react-example)\]
+        Howto and example for using Vizzu with **React**
+    - \[[vizzu-vite-demo](https://github.com/vizzuhq/vizzu-vite-demo)\] Howto and
+        example for using Vizzu with **Vite**
+    - \[[vizzu-pyscript-example](https://github.com/vizzuhq/vizzu-pyscript-example)\]
+        Howto and example for using Vizzu in **PyScript**
 
 Unofficial:
 
 - \[[christopher-caldwell/vizzu-vite-demo](https://github.com/christopher-caldwell/vizzu-vite-demo)\]
-  Starter template on running Vizzu with **Vite**
+    Starter template on running Vizzu with **Vite**
 - \[[triptych/hello-vizzu](https://observablehq.com/@triptych/hello-vizzu)\]
-  **Observable** Vizzu example
+    **Observable** Vizzu example