Repository navigation
Release 2.2.0 - #469
Merged
Merged
Release 2.2.0#469
Conversation
Closes apimatic/v4-test-automation#23 Adds the **nav.json** step from [v4-test-automation](https://github.com/apimatic/v4-test-automation) to `portal_tests.yml`, after **visual**: ```yaml - name: visual — nav.json if: ${{ !cancelled() }} working-directory: tests env: PLAYWRIGHT_BROWSERS_PATH: ${{ github.workspace }}\.playwright-browsers run: pnpm test:nav:visual ``` - For each nav.json layout in the QA RTM, it generates a copy of the suite's petstore build **with this commit's CLI**. It then checks the tab bar, the sidebar and the routes, and compares them against baselines (38 tests). - It runs 3 scenarios at once, and each serves on its own port (8090–8092). So it doesn't depend on the generate step or its server, and runs even if they failed. - In the test repo's CI this takes **~4.5–5.5 min**. It adds that to this job (~11 min today), which keeps it well inside the 45-min timeout. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: Shield-Jaguar <mujahiddaudkhan@gmail.com>
Release 2.2.0-beta.1
asadali214
requested review from
Shield-Jaguar and
saeedjamshaid
as code owners
November 5, 2026 04:44
|
mrafnadeem-apimatic
approved these changes
Nov 5, 2026
Contributor
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
Promotes beta to main, expected to publish 2.2.0 to the npm
latestdist-tag and mark the GitHub release Latest. The run commits nothing back to main; the tag goes on this merge commit. The candidate is 2.2.0-beta.1.Merge with Create a merge commit, once QA has passed on 2.2.0-beta.1.
What releases
Everything since v2.1.0: 2 commits.
#467 is a
cicommit and stays out of the notes.#465 also changes flags that 2.1.0 users may rely on, and goes out as a minor version because its title has no
!.sdk generateno longer takes--zipor--api-version, and its--destinationnames the SDK directory itself instead of a parent that gets<language>below it.--forceonsdk generateandsdk publishno longer asks: conflicts are resolved using the generator's changes, and an SDK that cannot be merged is replaced, with a warning.After the merge
back-mergejob merges main into dev; check that dev gains "chore: merge main into dev".npm view @apimatic/cli dist-tagsshowslatest: 2.2.0.sdk publish --destinationdefaults to<input>/sdk/<language>, andapi transform --forcediffers by a word. They need fixing in the docs repo.🤖 Generated with Claude Code