Repository navigation
chore: remove the deprecated qaseio package - #1021
Merged
Merged
Conversation
The legacy qaseio API client is no longer published or supported. All reporters and qase-javascript-commons use qase-api-client and qase-api-v2-client instead. - remove the qaseio workspace and its sources - drop it from the root workspaces list and package-lock.json - update the qase-javascript-commons README to name the current API clients
nismangulov
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the legacy
qaseioAPI client from the monorepo. It is no longer published or supported. Reporters andqase-javascript-commonsalready useqase-api-clientandqase-api-v2-client.qaseioworkspace and its sourcesworkspaceslist andpackage-lock.jsonqase-javascript-commonsREADME to name the current API clientspackage-lock.jsonalso picks up theqase-api-client1.1.16 andqase-api-v2-client1.0.12 versions from #1020. The lockfile onmainwas not updated after that bump.Why now
The axios 1.20.0 bump (#1019) fails CI only on
qaseio. Its generatedcreateRequestFunctionhas no return type, so declaration emit fails with TS2527. The API clients were already fixed in #1020. Removingqaseiounblocks #1019.Test plan
npm run build -ws --if-presentpasses