Skip to content

HARMONY-2237: Downgrade sqlite to fix error building in Bamboo.#876

Merged
chris-durbin merged 2 commits intomainfrom
harmony-2237-2
Mar 17, 2026
Merged

HARMONY-2237: Downgrade sqlite to fix error building in Bamboo.#876
chris-durbin merged 2 commits intomainfrom
harmony-2237-2

Conversation

@chris-durbin
Copy link
Contributor

@chris-durbin chris-durbin commented Mar 17, 2026

Jira Issue ID

HARMONY-2237

Description

HARMONY-2237: Downgrade sqlite to fix error building in Bamboo.

Local Test Steps

  • Make sure all tests are passing and build completes in Bamboo.
  • Make sure no vulnerabilities reported with npm run better-audit

PR Acceptance Checklist

  • Acceptance criteria met
  • Tests added/updated (if needed) and passing
  • Documentation updated (if needed)
  • Harmony in a Box tested (if changes made to microservices or new dependencies added)

Summary by CodeRabbit

  • Chores
    • Updated internal dependency version to improve system stability.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 17, 2026

📝 Walkthrough

Walkthrough

A sqlite3 dependency version is downgraded from ^6.0.1 to ^5.1.7 in the services/harmony package configuration. No behavioral changes or control flow modifications are introduced.

Changes

Cohort / File(s) Summary
Dependency Downgrade
services/harmony/package.json
Downgraded sqlite3 from ^6.0.1 to ^5.1.7 in dependencies.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • flamingbear
  • ygliuvt
  • indiejames

Poem

🐰 A version steps back with a hop and a bound,
From six to five point one, the new ground,
SQLite dances to yesterday's tune,
Under the moonlight so bright—hooray soon! 🌙

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: downgrading sqlite3 to fix a Bamboo build error, which matches the changeset.
Description check ✅ Passed The description includes all required template sections with relevant details about the Jira issue, purpose of the change, and test steps.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch harmony-2237-2
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Tip

CodeRabbit can use oxc to improve the quality of JavaScript and TypeScript code reviews.

Add a configuration file to your project to customize how CodeRabbit runs oxc.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
services/harmony/package.json (1)

157-157: Pin sqlite3 exactly and document in lockedDependenciesComments for CI stability.

The caret range ^5.1.7 allows drift to later 5.x releases, which could cause non-deterministic builds in CI. The lockfile currently resolves to 5.1.7 exactly, but pinning the version in package.json and documenting it in lockedDependenciesComments (following the established pattern in the file) prevents future drift.

Proposed change
-    "sqlite3": "^5.1.7",
+    "sqlite3": "5.1.7",
   "lockedDependenciesComments": {
+    "sqlite3": "Pinned to 5.1.7 to avoid Bamboo/native build regressions.",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@services/harmony/package.json` at line 157, Update package.json to pin the
sqlite3 dependency to the exact version "5.1.7" instead of using the caret range
"^5.1.7" and add an explanatory entry for this package under the
lockedDependenciesComments object; locate the sqlite3 line in
services/harmony/package.json, remove the caret from the version string (change
^5.1.7 to 5.1.7) and add a comment entry in lockedDependenciesComments keyed by
"sqlite3" describing that the version is pinned for CI/build stability to
prevent drift.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@services/harmony/package.json`:
- Line 157: Update package.json to pin the sqlite3 dependency to the exact
version "5.1.7" instead of using the caret range "^5.1.7" and add an explanatory
entry for this package under the lockedDependenciesComments object; locate the
sqlite3 line in services/harmony/package.json, remove the caret from the version
string (change ^5.1.7 to 5.1.7) and add a comment entry in
lockedDependenciesComments keyed by "sqlite3" describing that the version is
pinned for CI/build stability to prevent drift.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bdaed12c-d7b4-43d4-85cc-e4d826fb4d26

📥 Commits

Reviewing files that changed from the base of the PR and between e493494 and 7a59111.

⛔ Files ignored due to path filters (1)
  • services/harmony/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • services/harmony/package.json

@chris-durbin chris-durbin merged commit fa2ff67 into main Mar 17, 2026
6 checks passed
@chris-durbin chris-durbin deleted the harmony-2237-2 branch March 17, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants