v1.1.3

[Artmann]

Summary by CodeRabbit

• Chores
  • Version bumped to 1.1.3

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request bumps the extension version in package.json from 1.1.1 to 1.1.3. This is a configuration-only change with no functional code modifications.

Possibly related PRs

• v1.1.1 #181: Sequential version bump; this PR continues from 1.1.1 after the previous bump to 1.1.1
• v1.1.0 #179: Updates package.json version field
• v0.3.0 #145: Same type of change—updates the top-level version field in package.json

Suggested reviewers

• saltenasl

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	Title only states version number 'v1.1.3' without describing what changed or why; doesn't convey the actual change (version bump in package.json).	Use a descriptive title like 'Bump extension version to 1.1.3' to clarify the change intent.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between db84c27 and 1cfc7bb.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build & Test
• GitHub Check: Lint & Format

🔇 Additional comments (1)

package.json (1)

4-4: Version bump is valid, but PR context is sparse.

The version change from 1.1.1 to 1.1.3 is syntactically correct semver. However, the PR description ("Fixes #" with no issue reference) lacks context. For release clarity, consider including:

• Issue/ticket reference
• A brief release note or changelog entry
• Summary of changes included in 1.1.2 and 1.1.3

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73%. Comparing base (db84c27) to head (1cfc7bb).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #190   +/-   ##
=====================================
  Coverage     73%     73%           
=====================================
  Files        577     577           
  Lines      47626   47626           
  Branches    5596    5596           
=====================================
  Hits       34902   34902           
  Misses     10887   10887           
  Partials    1837    1837           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.