Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add proper info to the /status API response #1022

Merged
merged 3 commits into from
Jul 15, 2024

Conversation

mykola-mokhnach
Copy link
Contributor

Now, when the server part could be integrated into the application under test separately, it is important that the driver knows the server version to check it for possible compatibility issues.
Also, the response format itself has been updated to comply with W3C requirements

@mykola-mokhnach mykola-mokhnach changed the title feat: Add proper info to the /status API reponse feat: Add proper info to the /status API response Jul 14, 2024
@@ -98,9 +98,11 @@
"lint:server": "cd espresso-server && ./gradlew lint || cd ..",
"lint:fix": "npm run lint -- --fix",
"prepare": "npm run rebuild",
"sync-version": "node ./scripts/sync-version.js --package-version=${npm_package_version}",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, i didn't know of the npm_package_version

@mykola-mokhnach mykola-mokhnach merged commit 4602a6f into appium:master Jul 15, 2024
12 checks passed
@mykola-mokhnach mykola-mokhnach deleted the server_ver branch July 15, 2024 11:41
github-actions bot pushed a commit that referenced this pull request Jul 15, 2024
## [3.2.0](v3.1.0...v3.2.0) (2024-07-15)

### Features

* Add proper info to the /status API response ([#1022](#1022)) ([4602a6f](4602a6f))
Copy link

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants