fix package.json studio version

[gramian]

What does this PR do?

Update studio version in package.json and implicitly in package-lock.json

Motivation

Maven log

Checklist

• I have run the build using mvn clean package command
• My unit tests cover both failure and success scenarios

[gemini-code-assist]

Summary of Changes

Hello @gramian, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the version of the arcadedb-studio component. It specifically modifies the package.json and package-lock.json files to reflect an upgrade of the studio's declared version from 25.6.1 to 25.8.1. This ensures that the project's dependency manifest aligns with the intended studio version.

Highlights

• Studio Version Update: The arcadedb-studio version has been updated from 25.6.1 to 25.8.1 in both package.json and package-lock.json.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the version of the arcadedb-studio package from 25.6.1 to 25.8.1 in package.json and package-lock.json. The change is intended to align the frontend version with the backend Maven project version. My review includes a suggestion to also include the -SNAPSHOT suffix to fully match the Maven project's development version, which will improve consistency in versioning across the project.

[gemini-code-assist]

To maintain version consistency with the Maven project, it's recommended to align this version with the parent POM version specified in studio/pom.xml, which is 25.8.1-SNAPSHOT. Using a -SNAPSHOT suffix for development versions is a good practice to distinguish them from release builds. After changing this line, please remember to update package-lock.json by running npm install.

Suggested change

	"version": "25.8.1",
	"version": "25.8.1-SNAPSHOT",

[robfrank]

LGTM